Build AI agents that reach only what you allow.
Not your whole business. Not the open web.

A private AI agent is one that reaches only the knowledge bases, tools and connectors you explicitly bind to it, and nothing else. On Commt that boundary is enforced by the platform: there is no web-browsing or web-search tool on any agent, so it cannot reach anything you have not attached to it.

A Commt agent cannot browse or search the open web, because no web-browsing or web-search tool exists on the platform, for any agent on any plan. Connectors you enable, such as Slack or Jira, do make outbound calls to reach those specific services, but an agent can never reach anything beyond the tools and connectors you have explicitly scoped to it.

An agent reaches only the tools and connectors you scope to it, chosen from twenty available at launch. Examples include messaging and email tools such as Slack and Gmail, work tools such as Jira and Notion, and customer tools such as Salesforce and Zendesk, plus Zapier for reaching further tools and a direct API key for calling the agent from your own product.

No, RAG is optional on Commt: an agent can run on its instructions alone, or you can bind it to one or more knowledge bases so it retrieves from your own documents. When you do attach a knowledge base, the agent reads only the knowledge bases bound to it, never anything else in your account.

By default, Commt does not store your message content, only the metadata that produces your usage report: request counts, latency and which agent answered. Message text is written only when you switch on a time-boxed debug window or a conversation is flagged as a failure. You set your own retention period for what is kept, and deleting a record means either removing it outright or anonymising it.

Commt is hosted in the EU. Application, database and document storage run in the EU on private networking, with your files in isolated object storage and your vectors in an isolated database, neither reachable from the public internet.

Commt agents can use frontier models from Anthropic, OpenAI and Google, plus open-source models such as Llama and Qwen, through one integration. Your plan sets which models an agent can reach, and switching a model is a dropdown change, not a migration, so its instructions and knowledge bases carry over unchanged.

Running an agent costs your plan's monthly price: Entry is $244 a month for up to 5,000 requests, and Pro is $559 for up to 16,000, both 30 percent off list price during early access and locked for 12 months from the day you join. Entry works out at $0.049 a request and Pro at $0.035, with no separate usage bill, no per-token rate to model and no metered surprise, and when the requests included in your plan run out, your agents stop rather than billing you past it.

When an agent hits its plan's request limit, further requests stop immediately and return HTTP 402 with a machine-readable error code, so your application can show a fallback instead of hanging. Alerts go out at 50, 80 and 95 percent of the limit, the check runs before each request rather than after, and upgrading takes effect immediately from the dashboard.

No, unused requests do not roll over: the requests included with your plan apply to that billing month only. We would rather say so plainly than let you discover it on an invoice, and if you consistently use far fewer than your plan includes, you are probably on the wrong plan.

Commt does not sell credits, because a credit is a unit only the vendor controls, priced at a rate only the vendor knows, that could quietly change what it buys. A request is a unit you can count yourself: your plan includes a stated number of them each month, your agents stop when they run out, and there is nothing to convert or devalue.

On Enterprise, yes: you supply your own provider keys, Commt stores them encrypted and never exposes them again, and you keep your existing provider agreement. Commt still handles retrieval, versioning, limits and logs on top of your own keys.