Trademark Policy

Version 1.0 · Last revised: 2026-05-24

This policy explains how the trademarks, service marks, trade names, and logos of Kameas AI, Inc. (“Kameas”) may — and may not — be used. It applies to everyone, including users of the open-source Kenaz endpoints, customers of the Kameas Fleet product, partners, journalists, and the general public.

The Apache License, Version 2.0 (under which Kameas publishes the Kenaz Harness and the Kenaz Workbench / Kenaz Sandbox) expressly does not grant any trademark rights (see § 6 of that license). This policy is the document that governs trademark use; the Apache 2.0 license does not.

1. The marks we claim

Kameas claims common-law trademark rights in the following marks based on use in commerce, and (where indicated) has filed for federal registration with the U.S. Patent and Trademark Office:

Until a registration is issued by the USPTO, please use the ™ symbol (not ®) when designating these marks. Using the ® symbol on an unregistered mark is prohibited under 15 U.S.C. § 1111 and we ask that you not do so. We will update this page when registrations issue.

2. Use that does not require permission

You do not need our permission for the following uses, provided you do not suggest sponsorship, affiliation, or endorsement by Kameas where none exists, and provided the use is truthful:

• Nominative use to refer to our products. Saying that your tool “works with Kenaz™”, that your blog post is “about Kameas Fleet™”, or that your benchmark “compares Kenaz to other AI workbenches” is fine. Use the marks as adjectives, not nouns or verbs (“the Kenaz workbench”, not “a Kenaz” or “to Kenaz”), and follow the mark on first use with the generic noun that describes what it is.
• Truthful commentary, criticism, reviews, and news reporting. Including in headlines and excerpts. We will not assert trademark rights to suppress fair comment.
• Comparative advertising that is truthful and not misleading, in compliance with the FTC’s comparative-advertising guidance and analogous law in other jurisdictions.
• Personal, non-commercial expression. Stickers, t-shirts, hobby projects, conference badges, fan art that is clearly not made or endorsed by Kameas.
• Open-source project metadata that refers to our project. A README that says “a plugin for Kenaz™”, a package description like “Helm chart for Kenaz Workbench deployments”, or a topic tag like kenaz on a code-hosting platform.

3. Use that requires our prior written permission

You must get our written permission, in advance, before doing any of the following:

• Using the marks in the name of a product, service, company, organization, project repository, package, domain name, social-media handle, or app-store listing. Examples that are not allowed without permission: a product called “Kenaz Plus”, a company called “Kameas Cloud”, a repository named kenaz-fork on a public registry, an account named @kameas_official that is not us, the domain kenaz.io, or a npm/PyPI/crate package whose import name is kameas or starts with kenaz-.
• Using our logos in a way that suggests endorsement, certification, partnership, or affiliation (e.g., a “Kameas Partner” badge, a “Built for Kenaz” mark, a “Kameas Certified” designation, or any use of our logo on a product’s splash screen or marketing site as if we made it).
• Modifying our logos. Do not alter the colors, proportions, or geometry of the Kameas lattice mark. Do not animate it in a way that implies a feature of Kameas software. Do not incorporate it into a composite logo.
• Producing physical merchandise for resale that bears our marks or logos. Personal-use merchandise is fine (see §2); commercial-scale resale is not.
• Registering a domain name that contains the marks (e.g., kameas-cloud.com, kenaz-hosting.net). This includes purchases that combine the marks with generic terms (“cloud”, “hosting”, “official”, “support”, “app”).
• Using the marks in a way that creates likelihood of confusion with the source of Kameas products, including look-alike marks (KAMEEAS, KEN4Z, KAMEAS.AI in a way that suggests it is the official site), translations and transliterations intended to evade this policy, or stylizations that closely resemble our wordmarks.

To request permission, email legal@kameas.ai describing the proposed use, where it will appear, and the time period. We aim to respond within ten (10) business days.

4. Open-source forks of the Kenaz endpoints

The open-source Kenaz endpoints (Harness and Workbench / Sandbox) are published under Apache 2.0. You may fork, modify, redistribute, and create derivative works of the code in accordance with that license. You may not, however:

• name your fork in a way that uses the marks — e.g., a fork named “Kenaz Pro”, “Kameas Edge”, or kenaz-enterprise is not permitted;
• retain the Kameas lattice logo or the Kameas / Kenaz wordmarks in your fork’s readme, package metadata, splash screens, or distribution channels in a way that suggests the fork is the official Kameas distribution; or
• publish a fork to a package registry or app store under a namespace that uses the marks (e.g., kameas/… or kenaz-… on npm, PyPI, Homebrew, the Apple App Store, the Microsoft Store, Snap, Flatpak, etc.).

Acceptable fork names include things like kenaz-myname-fork (where it is clear from context that the fork is not Kameas’s official build) or a wholly new name. We are happy to confirm in writing that a particular fork name is acceptable; email legal@kameas.ai.

5. Enforcement and changes

We reserve the right to enforce these marks against use that creates a likelihood of confusion, dilutes the marks, or trades on Kameas’s goodwill. We aim to do so in the least adversarial way available — usually a polite email asking for a name change, with a reasonable transition period. We will not assert these marks against truthful, non-confusing reference use as described in §2.

This policy may change as our trademark portfolio evolves. The most current version is always at kameas.ai/trademarks. Material changes will be announced on the Site.

6. Contact

For trademark questions, permission requests, or to report a possible infringement, contact: