PRICING
You never spend more than you chose¶
Every capability is included from your first day. You pay for what you use: one cent per governed operation, on $5 of credit and no card. A spend ceiling is on from the day you sign up, and you can see it, change it, and be held to it.
What you pay for¶
| What | Meter code | Price |
|---|---|---|
| A governed operation | execution.operation |
$0.01 |
One line. EKKA does one thing: it decides whether an action is allowed, and proves it.
What you are never charged for¶
- A refusal. If EKKA says no, you pay nothing.
- A gate check. Deciding whether something is allowed is not billable work.
- Reading your own audit chain.
ekka audit verifyand every receipt check cost nothing, always. - A failed run. If work did not succeed, it is not counted.
- Your Enclave being connected. An always-on daemon is measured, never billed.
What's included¶
Every EKKA capability is available to your organization from the first day. Databases, AI models, files, your own APIs, MCP tools, programs on your own machine, and the encrypted vault. Nothing is held back to sell you a higher tier, because what we charge for is use, not access.
Paste any of these into ekka gate grant add --capability.
| What your agent can reach | Capability codes |
|---|---|
| Databases (read a row, list rows, write) | knowledge.postgres.readknowledge.postgres.listknowledge.postgres.write |
| AI models | llm.inferllm.act |
| Files on this machine | file.fs.readfile.fs.listfile.fs.write |
| Programs on this machine | process.invoke |
| Your own APIs | api.readapi.write |
| MCP tools | tool.mcp.readtool.mcp.invoke |
| The encrypted vault | secret.vault.read |
Your organization has all of them. You choose which agent gets which one, over which resource. See How governance works.
Secrets stay yours
Secrets live in your Enclave. Values never appear on the command line and never leave your machine. Govern authorizes the action without seeing the credential.
How big your organization can be¶
These bound what can exist, as against the spend ceilings further down, which bound what gets spent.
| What | Limit code | Included |
|---|---|---|
| People in your organization | org.members |
25 |
| Enclaves, the machines that run your agents | org.enclaves |
10 |
| Agents | org.agents |
25 |
An Enclave is a machine, so your laptop and a CI server are two of them.
These are soft. If your team is larger than this, write to contact@ekka.ai and we will raise them. They exist to bound an account nobody is watching, not to bound you.
Past one of these, the CLI names the limit it hit, what it is set to, and how to have it lifted. Everything you already have keeps running.
Larger organizations
EKKA Enterprise removes these ceilings and adds what a signed agreement needs. Write to contact@ekka.ai.
Hosted AI model usage¶
Inference through EKKA's hosted gate is a separate product with its own wallet and its own price. It does not draw on your EKKA credit. Your $5 is for exploring EKKA, and a new organization also holds $1 of AI credit.
| What | Meter code | Price | Per day |
|---|---|---|---|
| Input tokens | llm.tokens.input |
priced by model | 2,000,000 |
| Output tokens | llm.tokens.output |
priced by model | 400,000 |
Both meters are capped per day, so no run can build an unbounded bill. ekka org
billing shows the AI wallet and whether it is being charged; ekka org usage
shows the tokens counted.
Inference is billed from your AI wallet. The rates for these meters, in dollars per million tokens:
| Model | Input, per million tokens | Output, per million tokens |
|---|---|---|
anthropic/sonnet-4 |
$3.90 | $19.50 |
anthropic/opus-4 |
$19.50 | $97.50 |
anthropic/haiku-4 |
$1.04 | $5.20 |
openai/gpt-4.1 |
$2.60 | $10.40 |
What the provider charges us, plus 30%.
Bring your own key and you pay your provider directly. You still pay the operation price, because every operation crosses EKKA's control plane whether the model is ours or yours.
Your first $5¶
New organizations get $5 of credit, valid 90 days, and we do not ask for a card. At one cent per operation that is 500 governed operations.
It prints what is left and what has been spent this period.
When it runs out, work stops. Your organization is never overdrawn and never billed by surprise.
Adding credit
Credit is prepaid: you buy it, then work spends it. No invoice you did not ask for, and no card kept on file for automatic charges.
Credit is added to your organization by the EKKA team. Write to contact@ekka.ai to top up.
The ceiling you did not have to ask for¶
Every organization has a spend ceiling from day one. You did not opt in, and you do not have to remember it.
Your spend ceiling is $10 a day. In money, not in a count of something you would have to convert.
There are two kinds of ceiling and they answer different questions:
| Ceiling | What it bounds | Default |
|---|---|---|
spend.total |
money, across everything you are charged for | $10.00 a day |
execution.operation |
how many governed operations, whatever they cost | 1,000 a day |
execution.run |
how many plan runs. not priced | 200 a day |
The money ceiling is the one that caps your bill. The other two cap the rate, which is what stops a loop from burning a month of budget in an afternoon. 1,000 operations a day is at most $10 a day, so the two agree. The money ceiling is the one to read, because it stays true whatever an operation costs.
See yours, and change it:
$ ekka org limits
EKKA stops work when a ceiling is reached. These bound how much gets spent;
`ekka org edition` shows what can exist.
METER USED PERIOD SET BY
execution.operation 8 / 1000 day EKKA default
execution.run 40 / 200 day EKKA default
llm.tokens.input 0 / 2000000 day EKKA default
llm.tokens.output 0 / 400000 day EKKA default
spend.total $0.08 / $10.00 day EKKA default
$ ekka org limits set spend.total 25
spend.total per day is now $25.00 (was EKKA's default).
Recorded in your audit log, and the organization's owner has been emailed.
check the record ekka audit list
For spend.total you type dollars, so set spend.total 25 is a twenty-five
dollar cap. For the other meters you type a count. Each row on that screen shows
its own unit, so read it first and type the same kind of number.
Lower it whenever you like. Raising it is an admin decision, it is written to
your own audit chain, and the owner is emailed even when the owner made the
change. Read it back with ekka audit list.
Past a ceiling, new work is refused and told which ceiling stopped it. Anything already running keeps running.
Self-hosting¶
Running EKKA yourself does not make it free. You pay per governed operation either way, because the governance is the product and it is the same control plane doing the same work.
What self-hosting changes is where your data and your credentials live, not whether the meter runs. See What leaves your machine.
Checking any of this yourself¶
Every number on this page is readable from the CLI.