PRICING
Set a spend ceiling from day one¶
Every capability is included from your first day. Every edition runs models on your own model key. Developer, the edition every new organization starts on, is free: 1,000 runs a month, and no card. On EKKA Enterprise you pay for what you use, one cent per governed operation. A spend ceiling is on from the day you sign up, and you can see it and change it.
What you pay for¶
On Developer, runs are never charged: see Developer below. On EKKA Enterprise:
| 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 refused operation. An operation EKKA refuses is not billable. Earlier successful operations remain billable.
- 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 operation. An operation that does not complete successfully is not billable. A successful operation remains billable even if a later step or the overall run fails. On Developer, a run counts toward the month's 1,000 once EKKA admits it, whether it then succeeds or fails.
- 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, agents working on their own desks, your company's own systems, the encrypted vault, your organization's memory, and a person's approval before an agent acts. 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.writefile.fs.extract |
| Programs on this machine | process.invoke |
| An agent working on its own desk (a workspace NVIDIA OpenShell isolates on your own machine: the agent does one approved job there and reaches only the services you connected) | job.run |
Your company's own systems (read or list records, for example hr.salary, from a Business API you connected to a shelf) |
shelf.read |
| Your own APIs | api.readapi.write |
| MCP tools | tool.mcp.readtool.mcp.invoketool.mcp.write |
| The encrypted vault (sign with a key you stored there; the key is used and never returned) | secret.vault.sign |
| Ask a person before the agent acts (the run pauses, a person in a role you named chooses from the answers you wrote, and the agent carries on with their choice) | human.decision.request |
| Memory your organization keeps (the agent reads what it learned last time, lists what is there, and adds to it; you choose which shelf each kind of record is filed on) | memory.readmemory.listmemory.write |
| The agent's own encrypted store (its own tables inside your Enclave: read its rows, list its tables, add new rows) | store.readstore.liststore.write |
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. The Enclave holds the credential and adds it to the call. EKKA's records do not contain it.
How big your organization can be¶
These bound what can exist, as against the spend ceilings further down, which bound what gets spent. An Enclave is a machine, so your laptop and a CI server are two of them.
Developer¶
A new organization starts on Developer, the free edition for one person.
It includes every capability under What's included,
among them an agent working on its own desk (job.run) and your company's own
systems (shelf.read).
| What | Limit code | Included |
|---|---|---|
| People in your organization | org.members |
1 |
| Enclaves, the machines that run your agents | org.enclaves |
1 |
| Agents | org.agents |
25 |
| Runs | execution.run |
1000 a month, never charged |
| Your organization's own prompts | org.prompts |
200 |
| Versions of one prompt | org.prompt_versions |
100 per prompt |
| Prompt versions created | prompt.published |
60 a day |
| End users of your apps | end_users.monthly_active |
100 a month |
Runs on Developer are never charged. When a month's runs are used up, EKKA refuses the next run, says when the count starts again, and charges nothing. Scheduled plans start no new runs before the count starts again. Your agents, Enclave and records stay as they are. To run more, write to [email protected] about EKKA Enterprise.
The prompt rows count the prompts your organization writes for its own plans. They are there to stop runaway use, not to price anything. A day starts at 00:00 UTC, and deleting a version does not give back that day's count.
End users are people outside your organization, such as a client's employees, who run the plans you expose to them through an app. Each person counts once a month, however often they ask. When a month's 100 are reached, people already counted keep working, and a new person is refused until the count starts again on the 1st, at 00:00 UTC.
Past one of these, the CLI names the limit it hit, what it is set to, and how to have it lifted.
EKKA Enterprise¶
For a team: more than one person or more than one Enclave, under a signed agreement, with every capability Developer has. Write to [email protected].
| What | Limit code | Included |
|---|---|---|
| People in your organization | org.members |
unlimited, unless your agreement sets one |
| Enclaves, the machines that run your agents | org.enclaves |
unlimited, unless your agreement sets one |
| Agents | org.agents |
unlimited, unless your agreement sets one |
| Your organization's own prompts | org.prompts |
unlimited, unless your agreement sets one |
| Versions of one prompt | org.prompt_versions |
unlimited, unless your agreement sets one |
| Prompt versions created | prompt.published |
unlimited, unless your agreement sets one |
| End users of your apps | end_users.monthly_active |
unlimited, unless your agreement sets one |
ekka org limits # every ceiling in force, in its own unit
ekka org edition # which edition your organization is on, and what it carries
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.
Every edition runs models on your own key, and you pay your provider directly. The rates below are for EKKA's hosted AI.
| 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. On EKKA Enterprise you still pay the operation price, because every operation crosses EKKA's control plane whether the model is ours or yours.
Credit on EKKA Enterprise¶
On EKKA Enterprise, operations are paid from your organization's credit. On Developer there is nothing to pay for, so there is no credit to buy.
It prints what is left and what has been spent this period.
When it runs out, new work is refused. Credit is prepaid, so there is no surprise invoice.
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 [email protected] 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 your Enclave yourself does not change the price. Each edition costs the same wherever it runs: on Developer, runs at no charge; on EKKA Enterprise, one cent per governed operation. 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.