elan1 RUN · RUNTIME CONTROLS
elan1 Run Runtime Controls, with elan1 Govern built in.
elan1 Run Runtime Controls is the module that controls model and tool calls at runtime, with elan1 Govern built in. It applies a budget hard-stop, attributes cost to a tenant and process, runs a guard on each call and authorises tool use. A call refused at the edge returns a 409 before the first token and costs 40% of one governed action: ₹0.64 at the L1 rate.
Available now, in every elan1 Run subscription.
01What it does
Six controls on every call.
- Budgets
- Virtual keys and hard-stop budgets, reserved at the edge before the first token.
- Attribution
- Tenant, team and use case on every call, for chargeback.
- Guard
- PII detection and redaction, provenance tagging and injection defence. Each guard decision is code reading a declared policy, and its reason comes from that policy, never from a model. A policy cannot go live until it has been simulated.
- Tools
- Every tool call carries an actor and an autonomy ceiling. There is no anonymous tool call. Quarantine stops a call in flight.
- Runtime evidence
- A trace audit trail, a licence register pinned at exact commits, and a nightly isolation attack.
- Stops
- A stopped call returns a 409 with the policy's stated reason, before the first token. It costs 40% of one governed action.
Send calls against a budget.
Budget is reserved before the first token. Send five illustrative calls; the fifth needs more than is left, so it stops at the edge.
2,00,000 tokens this month
virtual key vk_specimen_finance_opspol_specimen_budget · v3hard stop at the edgereserved before the first token
| Call | Reservation | Outcome |
|---|---|---|
| call_specimen_0101Match 120 supplier invoices to purchase orders | 42,000 | Waiting |
| call_specimen_0102Match 96 supplier invoices to goods receipts | 38,000 | Waiting |
| call_specimen_0103Explain 14 three-way match exceptions | 61,000 | Waiting |
| call_specimen_0104Match 110 supplier invoices to purchase orders | 47,000 | Waiting |
| call_specimen_0105Summarise this week's unmatched invoices | 18,000 | Waiting |
Response at the edge
No call sent yet. Each call reserves its estimate before the first token reaches the model.
Send a call to reserve its tokens. The fifth call needs more than is left.
02Who it's for
People who answer for the model bill and the tool calls.
- CISOs and platform teams who must show who called which model or tool, and at what cost.
- CFOs who want a budget that stops spend before it happens.
03How it works
The call on one side of the hairline, the write on the other.
Six steps from the edge to the record. Tap, hover or focus a step to see which side of the hairline it sits on.
Runtime controls: the call
Action governance: the write
- 01 The call
The edge checks tenancy, region and token. An agent with no sponsor is stopped: ‘This action needs a person behind it.’
- 02 The call
Budget is reserved before the first token.
- 03 The call
The guard checks the input. Its verdict is an input to Govern, never the allow.
- 04 The call
The tool call is checked against its actor and autonomy ceiling.
- 05 The write
If the call proposes a business write, the intent goes to elan1 Govern. The approval wait is held on the run contract, and expiry means refusal.
- 06 The write
Govern allows or refuses and writes its proof record. Trace spans bind to it.
04In the console
Runtime Controls, as the console shows them.
One call span by span, every stopped call grouped by the policy that stopped it, and the spend behind every call.
Illustrative specimen. Not customer data. Fictional sandbox data from the console design.
05What it connects to
Five contracts, the set Govern needs.
elan1 Run can prove a call happened. Only elan1 Govern can prove it was allowed.
Runtime Controls run on five contracts (gateway, trace, tools, run and guard), the set Govern needs. Govern runs as a separate service on the same runtime, and you buy one thing. Writes go through elan1 Govern. elan1 Run’s own tooling connects in Mode B: evaluated and recorded, failing closed if elan1 is unreachable.
Writes go through elan1 Govern.
06What it costs
In every subscription. A stopped call costs 40% of a governed action.
The unit
One node-year
Per node and per GPU. Runtime units are counted and shown, never priced.
Runtime Controls are included in every elan1 Run subscription. The governance profile, which runs them with elan1 Govern built in, adds three nodes under management at ₹5,40,000 per year. A call stopped at the edge costs 40% of one governed action: ₹0.64 at the L1 rate. Writes that pass through elan1 Govern are governed actions, Govern's unit, and a write that Govern refuses is metered by Govern at 40% of one.
| What | Price · excl. GST | Includes |
|---|---|---|
| Starter | ₹1,80,000 per year | 2 CPU nodes included |
| Standard | ₹6,00,000 per year | Plus nodes and GPUs under management |
| Sovereign | ₹24,00,000 per year | Plus nodes and GPUs under management |
| CPU node under management | ₹1,80,000 per node per year | |
| GPU under management | ₹1,80,000 per GPU per year | |
| elan1 Run Runtime Controls, with elan1 Govern built in | ₹5,40,000 per year | The Runtime Controls module is included in every subscription; the governance profile adds three nodes under management (contracts C2, C6, C7, C8, C10) |
| Paid 90-day pilot | ₹4,50,000 | |
| A call refused at the edge | 40% of one governed action (₹0.64 at the L1 rate) | Returns a 409 before the first token, so no token is sent |
All prices are exclusive of GST. Prices are current list prices; GST is added at the applicable rate on the invoice.
- Governed actions are billed by elan1 Govern at the rate for your level. All prices are exclusive of GST.
All prices are exclusive of GST. GST is added at the applicable rate on the invoice.
07Status
Available now, in every subscription.
Available now.
- Five contractsgateway, trace, tools, run and guard: the set Govern needs.Status: Available
- Govern built inelan1 Govern runs as a separate service on the same runtime.Status: Available
- Governance profileAdds three nodes under management at ₹5,40,000 per year.Status: Available
08What it does not do
What Runtime Controls do not do.
- It does not approve business writes. Only elan1 Govern allows or refuses.
- It does not treat a guard verdict as an approval.
- It does not let memory affect a policy decision.
- It does not make you compliant with the EU AI Act or any other law.
09FAQ
Six direct answers.
The call stops before the first token: the budget hard-stop applies at the edge, and cost is attributed by tenant, team and use case. A call refused at the edge returns a 409, no token is sent, and it costs 40% of one governed action: ₹0.64 at the L1 rate.
Each tool call is checked against your declared policy before it runs, with an autonomy ceiling. Code reading that policy makes the decision, not a model, and any write that follows goes through elan1 Govern.
Yes, at a reduced rate. A call refused at the edge returns a 409 before the first token, so no token is sent. It costs 40% of one governed action: ₹0.64 at the L1 rate. A write that elan1 Govern refuses is metered once, by Govern, at the same 40%. The Runtime Controls governance profile itself is ₹5,40,000 a year, exclusive of GST.
It controls the runtime: calls, cost, components, licences and tools. Approving business actions is elan1 Govern's job, and Govern comes built in.
No. You buy elan1 Run Runtime Controls. Govern runs behind it as a separate service.
No. Classifiers may detect PII, but code reading your declared policy makes the decision.
10Next steps
Where to go from here.
Next steps
One write path, four layers
Work and Decide propose. Govern and Run assure. Only Govern allows.
// elan1 RUN · RUNTIME CONTROLS
elan1 Run Runtime Controls, with elan1 Govern built in.
See a write take the Right Path, or start a paid 90-day pilot with budgets, guard and tool limits on your stack.