Solution · For enterprise
Your legal team needs a contract and a say in where agent data lives. Pick where it runs, on a yearly contract.
Enterprise runs on a yearly contract, on our cloud, a dedicated instance or your own Cloudflare account. One Protect policy covers the org.
We want contract terms, not a card.
Where it runs
- Our gateway
- Our cloud
What you get
- A yearly contract
- Requests set in the contract
- Every feature
Enterprise Cloud. Your own Anthropic or OpenAI account pays the model. We add no fee on tokens.
We want a gateway that is ours alone.
Where it runs
- Your own gateway
- In our Cloudflare account
What you get
- Its own hostname
- Its own secrets
- Every feature
Enterprise Dedicated, on a yearly contract.
Our data must stay in our account.
Where it runs
- The same gateway
- Deployed in your Cloudflare account
You hold
- The data
- The keys
- The logs
- The Cloudflare bill
There is no on-premises build.
An engineer's agent tries to read .env.
Set once by the org. An agent cannot loosen it.
Blocked by your team’s policy: Read environment files. .env files hold secrets.
Every member's agents follow it, on every machine.Protect checks each tool call before your client runs it.
A script with an API key tries to turn Protect off.
API key: turn Protect off 403 A change that loosens the policy needs a person signed in to the console, and a reason.
An API key can only tighten the policy. Every change goes into a hash-chained history.
The auditor asks what the agents tried.
A decision log row holds
- Time and decision
- Rule, tool and program
- Host, project, session
- Policy version
It never holds
- Command text
- Flag values
- Environment values
- File contents
Export as CSV or JSON Lines. Keep rows for 1 to 365 days.
Every agent has its own rules. No one place to set them.
Each client has its own rules, set on each machine.
When security asks what the agents tried, there is no single log to show.
Legal and security want a contract, and a say in where the gateway runs and who holds the data.
Three ways to run Enterprise. All on a yearly contract.
| Enterprise Cloud | Enterprise Dedicated | In your Cloudflare account | |
|---|---|---|---|
| Gateway | Our gateway | Your own gateway | The same gateway, deployed in your account |
| Runs in | Our cloud | Our Cloudflare account, with its own hostname and secrets | Your Cloudflare account |
| What sets it apart | Contract terms | A gateway that is yours alone | You hold the data, the keys, the logs and the Cloudflare bill |
| Protect | One policy for the org | One policy for the org | One policy for the org |
From Plans and limits and Pricing. Requests are set in the contract. Each member's memory stays their own.
Tested on production. Read the run.
The run used single accounts. It did not test the org-wide Team policy.
Throwaway accounts in production, no customer traffic. Read the run →
One hop for every request. One policy on that hop.
- 01Connect each machine
Each engineer runs
npx @context-mode/cli. It connects Claude Code and Codex and keeps a backup of the old config. - 02Pick where it runs
Our cloud, a dedicated gateway, or your own Cloudflare account. The contract sets your requests.
- 03Read the log
Every block goes into a decision log with its rule, tool and host. Export it as CSV or JSON Lines.
What we do not ship today. So you can plan.
No SSO, SCIM or team roles yet. One Protect policy per account.
The gateway runs on Cloudflare: ours, a dedicated instance, or your own account.
Claude Code and Codex. Other agents that go through the gateway are recorded, not enforced.
Protect checks only requests that go through it. Codex cannot be pinned to it today. See Keep the gateway on.
A script file, a compiled program or a payload decoded at run time gets past Protect. Keep your agent's sandbox on.
Stored prompts have no automatic expiry yet, and the console has no delete or export button. Ask us and we delete your account's data.
What this uses.
Checks every tool call before your client runs it. One policy for the whole org.
Team gives one policy and one bill. Enterprise adds a contract and a choice of where it runs.
The three Enterprise ways, and what pauses at a limit.
Related: Secure coding agents, For platform teams, For startups.
One policy for every agent. Talk to us about the contract.
Write to us for a yearly contract. To try it first, npx @context-mode/cli connects your agents. 1,000 requests free, no card.