OpenBot Trademark Policy

Which names and logos this covers

Our names and logos means these four things:

• OpenBot™, also called CopilotKit OpenBot™, our open-source software for AI coworkers and the project around it.
• OpenBot for Business™, our paid offering built on CopilotKit OpenBot.
• CopilotKit™, our company and our products.
• The OpenBot and CopilotKit logos.

CopilotKit OpenBot, OpenBot, OpenBot for Business and CopilotKit are trademarks of Tawkit, Inc., which does business as CopilotKit, for our software and services. In this policy, every rule about OpenBot also applies to CopilotKit OpenBot. We use the ™ symbol with these names. The rules in this policy apply whether or not a name is registered.

Can I do this?

Yes means you can do it without asking. Ask first means you need our written permission before you start. We say yes in some cases and no in others. Some rows say whether we expect to say yes or no. No means we do not permit it, except where the row says otherwise.

A changed version (also called a fork) is a copy of CopilotKit OpenBot with your own changes.

Each row is a short answer. The section it links to is the full rule, and it decides if the two ever differ.

The rule behind everything

When you use our names and logos, make sure nobody is misled about what they are getting or who it comes from. Everything below is this rule applied to common cases.

The code license is not a trademark license

The CopilotKit OpenBot code uses the MIT License. That license lets you use, copy, change and share the code. It does not give you the right to use our names or logos. This policy is where you get those rights.

Always keep our copyright and license notices, as the MIT License requires. Keeping those notices, or saying truthfully that your version is based on OpenBot, never needs permission.

What you can do without asking

Talk about OpenBot

Write about it, teach it, review it or compare it, in articles, books, talks, videos and docs. You can use the name in the title of your book, article, talk or video, for example "A Guide to OpenBot". You can use the name OpenBot in ordinary sentences to say truthfully what you use or do, such as "we run ten OpenBot instances". You can show our logo, unchanged, as long as it does not look like the logo of your own product. This includes slides you present at a paid or sponsored event. Do not suggest that we wrote, sponsored or approved your work. A title may start with OpenBot, as in "OpenBot in Action", if the work is about OpenBot. On a website, link the logo to the OpenBot project page. Talking about CopilotKit follows the same rules as talking about OpenBot.

Say how your work relates to OpenBot

Use our name after a word that says how your work relates to it:

• "Acme Agent works with OpenBot"
• "Acme Agent for OpenBot"
• "Built on OpenBot"
• "Compatible with OpenBot"
• "Based on OpenBot"
• "Powered by OpenBot"

Put our name last. Write "Acme Agent for OpenBot", not "OpenBot Acme". The same rule applies to CopilotKit: "Acme for CopilotKit" and "works with CopilotKit" are fine. "CopilotKit Acme" is not.

Offer services about OpenBot

"Acme: OpenBot consulting" is fine if you do not suggest that CopilotKit partners with you, runs it or approves it. Describing yourself as an "OpenBot consultant" is fine under the same condition. You can run a paid course, workshop or conference about OpenBot and name OpenBot as its subject, for example "Building agents with OpenBot" or "Learn OpenBot". Ask us first if you want to use our logo in its name, branding or ads, or a name that suggests we run or approve it.

Share unmodified OpenBot

If you share an official release exactly as we published it, you can keep its name and logos.

Refer to OpenBot for Business

You can refer to our OpenBot for Business offering by name.

Make narrow changes and keep the name and logos

You can keep the OpenBot name and logos if your changes are only of these kinds:

• You package OpenBot for an operating system, a package manager or a container image, for example a Docker image called openbot-arm64.
• You port it to another platform.
• You apply fixes that we have already published.
• You host a fork only to propose changes back to us.

Say clearly what you changed. Do not promote a fork that exists only to propose changes. That means you do not announce it, publish releases or packages of it, or list it in a store or directory as something to use instead of OpenBot.

Use a changed version inside your own company

You can use a changed version of OpenBot inside your own company without asking us. The MIT License allows the code use, and you can leave our name and logos in it. The rules about sharing a changed version apply when you share it with people outside your company.

Share a changed version under its own name

You can share a changed version under its own name, for example "Acme Agent (based on OpenBot)", if you give it its own name and logo, take our logos out of it, and say it is based on OpenBot. Your own name ("Acme Agent") is the name of the product. OpenBot must not be that name or its first word. The words "based on OpenBot" after your name are a description, and they can stay.

Giving your changed version its own name means you change the published package name (for example on npm, PyPI or Docker Hub) and every product name users see: the app title, the About screen, the website and the docs. Internal module names, import paths and code identifiers that say openbot can stay. Before you install a package that says OpenBot, check that CopilotKit published it. Our official channels are listed under "What we do not allow", in the item "Calling your build official".

Run a community meetup

You can name a group "[City] OpenBot Meetup". The group must be about OpenBot, it must be free or charge only to cover costs, and it must make no profit. Sponsors can pay for the venue or food, as long as the group makes no profit. The group can use a social media handle with its city in it, such as @OpenBotBerlin. The profile must say it is a community group and is not run by CopilotKit. A domain name for the group needs our permission.

Use openbot in code

You do not need permission to use the word openbot or copilotkit in file names, import paths and code identifiers, or in the name of a repository that holds your own project, your own copy, your own settings or a fork you keep to send changes back to us, such as my-openbot-config or my-copilotkit-app. A published package or plugin name that contains openbot follows Name tools that work with OpenBot. A published package or plugin name that contains copilotkit needs our permission.

Name tools that work with OpenBot

A package, plugin or repository name that starts with openbot- is fine for a tool, example, tutorial or starter project that works with OpenBot, if you do not present it as official. The rest of the name must say what your tool does, such as openbot-slack. Names such as openbot-pro, openbot-official and openbot-cloud are not allowed, because they look like ours. A published package or plugin name that contains openbot in any other form, such as openbot alone or openbotpro, needs our permission. The display name still puts our name last, as in "Slack plugin for OpenBot". This is the exception to the rule that OpenBot may not be the first word of a name. For a published package or plugin name that contains copilotkit, ask us first. We expect to say no to names that look official.

Run your own copy

You can use an address such as openbot.example.com for your own team or company's copy of OpenBot, where only your team or company uses it.

Make personal merchandise

You can make a T-shirt or sticker for yourself or your friends, or to give away free at a community event. Use our logos as they are.

What you need our written permission for

A changed version under the OpenBot name

If you share a changed version with people outside your company, and your changes go beyond the kinds listed under Make narrow changes, give it its own name and logo. You can still say where it came from: "Acme Agent (based on OpenBot)". If you want to call your changed version OpenBot, ask us.

A hosted service or paid software product

You can say truthfully what it does, for example "Acme Cloud runs OpenBot". A name for a hosted service or a paid software product that starts with OpenBot or CopilotKit, or that could make people think we run it, needs our permission, for example "OpenBot Cloud" or "Acme OpenBot Cloud". To use our logo in its ads, ask us first. Consulting, training, courses and workshops follow Offer services about OpenBot instead.

Domain names, social media handles, channel names and service names

Domain names, social media handles, GitHub organization names, channel names (such as a YouTube channel) and service names that contain our names, that you offer to the public, and that could make people think they are ours, such as openbot-cloud.com or @OpenBotHelp, need our permission. The exceptions are an internal address where you run your own copy of OpenBot for your own team or company, and a community group's city handle, described under Run a community meetup.

Merchandise for sale

Selling merchandise with our names or logos needs our permission. Selling merchandise at cost still counts as selling.

Events and courses

Events and courses that use our logo in their name, branding or ads, or that have a name suggesting we run or approve them, need our permission. We expect to say no unless we run or co-run the event. A name with "official" is never allowed. Showing our logo in slides you present is covered under Talk about OpenBot.

Changed logos

Changing our logo, including new colors or remixes, needs our permission.

What we do not allow

Most of these are about avoiding confusion. If you are unsure, ask.

• Implying we endorse you. Do not suggest that CopilotKit made, sponsors, certifies, partners with or approves a product, service, company or event. Only a written agreement with us allows it.
• "Certified" or "approved". Do not say your product is certified, approved or endorsed for OpenBot or by CopilotKit. We do not have a certification program. Saying it is "Compatible with OpenBot" is fine.
• Look-alike names. Do not use a name that imitates ours, such as "OpenB0t" or "0penBot", for software or services.
• Our names as part of your name. Do not use OpenBot, OpenBot for Business or CopilotKit as the first word or the main word of your product or company name. Examples we do not allow: "OpenBot Acme" and "OpenBot Pro". You can describe your work with "for OpenBot" or "works with OpenBot" after your own name, as in "Acme Slack for OpenBot". We allow an exception only if we agree in writing, so ask us. A name for a hosted service or a paid software product that starts with OpenBot or CopilotKit, or that could make people think we run it, needs our permission. Consulting, training, courses and workshops follow Offer services about OpenBot instead. This does not apply to the title of a book, article, talk or video about OpenBot (see Talk about OpenBot).
• OpenBot for Business as your own name. Do not use this name, or a similar name, for your own product or service. You can still refer to our OpenBot for Business offering by name.
• Registering our names. Do not file a trademark application for any of our names or logos, in any country.
• Calling your build "official". Only releases, packages and services that CopilotKit publishes are official OpenBot. That includes the code at github.com/CopilotKit/OpenBot, the images under ghcr.io/copilotkit, the copilotkit and @copilotkit packages on npm, and www.copilotkit.ai. Anything else is not official, even if it uses OpenBot code. Do not use words such as "official", "original" or "only" in your name. This stays true even if we gave you permission to use the name.
• False or misleading use. Do not use our names or logos in a way that is false or misleading. Do not use them on software that does not follow the MIT License, for example software that removes the license notice.

How to write our names

• Write OpenBot as one word with a capital O and a capital B. Write CopilotKit with a capital C and a capital K.
• Use OpenBot as a name. Do not turn it into a verb or a common noun. Write "OpenBot software" or "the OpenBot docs", not "to openbot a file" or "an openbot".
• In your own materials, you do not need to add ™, but you may.
• Keep your own name more prominent than ours.
• If you use our names with permission, add this line: "CopilotKit OpenBot, OpenBot and CopilotKit are trademarks of Tawkit, Inc. (doing business as CopilotKit). Used with permission."

Logo rules

• The logo files are in the CopilotKit OpenBot repository: desktop/src-tauri/icons. They are in the code, but this policy, not the MIT License, decides how you can use them as our logos.
• Unless we give you permission in writing, do not change the shape, proportions, colors or lettering. Do not add effects. Do not combine our logo with another logo.
• Leave clear space around the logo, and keep it readable.
• On your website, link our logo to the OpenBot project page.
• If you make changes beyond the kinds listed under Make narrow changes and share your changed version with other people, take our logos out of it. Also take OpenBot out of its product name and the other names users see, such as the app title and the About screen, unless we gave you written permission to keep it. A line saying your version is based on OpenBot, as in "Acme Agent (based on OpenBot)", can stay.
• Do not use our logo as the icon of your own app, favicon or profile picture. An unmodified OpenBot or a narrow-change package keeps its own icon. Using our logo this way makes your product look official.

How to ask for permission

Email trademarks@copilotkit.ai and tell us three things:

1. Who you are.
2. What you want to do and where. A link or a mock-up helps.
3. Whether you charge money for it.

If we do not reply, that does not mean yes. You have permission only when we give it to you in writing.

How to report misuse

Email trademarks@copilotkit.ai with a link and a short description. We will look at each report.

Changes to this policy

We may update this policy. The date below shows the latest version. If a change stops a use we allowed before, we will give you reasonable time to change it. Written permission we gave you stays valid under its own terms.

Your legal rights and ours

The permissions in this policy are not exclusive and cannot be transferred. They last only while your use follows this policy. We may ask you to show us how you use our names and logos. If your use does not follow this policy, or harms the quality people expect from OpenBot, we may ask you to change it or stop, and you must do so. Nothing in this policy limits rights the law gives you.

This policy tells you what we allow. It does not take away any right the law gives you, such as fair use. If this policy does not cover your use and the law does not already allow it, ask us before you go ahead.

This policy is about our names and logos as used for the CopilotKit OpenBot software at github.com/CopilotKit/OpenBot and for services built on it. It does not cover names that do not contain or imitate our names.

Any goodwill your use creates in our names and logos belongs to Tawkit, Inc.

Last updated: 03Nov2026.

Adapted from the Model Trademark Guidelines, available at www.modeltrademarkguidelines.org, licensed under CC BY 4.0. We changed the guidelines to fit OpenBot and CopilotKit.