elan1 RUN · SUBSTITUTION
Replace a component without rebuilding the integration.
elan1 Run Substitution replaces one component of the AI stack, such as a model or vector store, with another that meets the same fusion.*/v1 contract. It follows nine steps with two human gates, H1 and H2, and is never autonomous. Applications keep calling the contract, so the integration does not need to be rebuilt.
Available now, in every elan1 Run subscription.
01What it does
Projects get archived, relicensed and acquired. Your integration should not notice.
A substitution starts from a recorded trigger: a licence change, an archived project, a CVE, an SLO breach, cost, your request, a scheduled upgrade, an outage or a failed substitution. Rollback is its own trigger. Scheduled changes ride an upgrade train with ten working days' notice.
- A licence change
- An archived project
- A CVE
- An SLO breach
- Cost
- Your request
- A scheduled upgrade
- An outage
- A failed substitution
02Who it's for
Teams who must move off a component, and show what changed.
- Platform teams who must move off a component quickly and show what changed.
- SIs and GPU operators who run the same change across many tenants.
03How it works
Nine recorded steps. Two named people decide.
Step 5 belongs to the conformance suite. Step 7 opens into four parts: the proposal, H1, an elan1 Govern gate check and H2.
Not started. Show the next step to begin; the walk stops for each named person.
- Step 1.
Trigger, recorded with its reason.
- Step 2.
Scope: the tenants and contracts affected.
- Step 3.
Plan: the cost change, shown in rupees first.
- Step 4.
Sandbox: the substitute runs against a copy.
- Step 5.
Prove: the conformance suite alone decides. Red stops here.
- Step 6.
Shadow: the substitute runs beside the live one: 72 hours for stateless and registered contracts, 7 days for indexed ones, a replay of at least 200 runs for in-flight work.
- Step 7.
Propose and decide: four parts, two of them human gates.
- 7.1the proposal
- 7.2Human gateH1, your registered approver, never an elan1 Run employee
- 7.3an elan1 Govern gate check: allow, allow with approval required, or refuse
- 7.4Human gateH2, a named elan1 Run decider who did not brief the agent.
- Step 8.
Promote: only the Promoter, the one component that holds live credentials, applies the change.
- Step 9.
Record: a ledger row. A substitution without a completed ledger row did not happen.
Illustrative specimen. Not customer data. The walk is simulated in this browser; in elan1 Run each step is recorded with its evidence.
04In the console
A substitution, as the console records it.
The record moving through nine steps, a plan closed at Gate 1 by a red blocking class, and the second human gate.
Illustrative specimen. Not customer data. Fictional sandbox data from the console design.
05What it connects to
Conformance at step 5. elan1 Govern at step 7.3.
Step 5 is Conformance. Step 7.3 asks elan1 Govern, over KernelPort in Mode B: evaluated and recorded. If Govern is unreachable, step 7 does not go ahead on a timeout. Writes go through elan1 Govern. An agent may draft the plan, but it holds no credentials and decides nothing.
Writes go through elan1 Govern.
06What it costs
Included in every subscription.
The unit
One node-year
Per node and per GPU. Runtime units are counted and shown, never priced.
Substitution is included in every elan1 Run subscription. Step 3 shows the cost change before anyone decides.
| 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 | |
| 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.
All prices are exclusive of GST. GST is added at the applicable rate on the invoice.
07Status
Available now.
Our target: a live substitution with no change to consumer code, inside 72 hours. A target, not a measurement.
- Nine stepsTwo human gates, H1 and H2. Never autonomous.Status: Available
- Gate checkStep 7.3 asks elan1 Govern, over KernelPort in Mode B: evaluated and recorded.Status: Available
08What it does not do
What Substitution does not do.
- It does not run without two named people.
- It does not skip the proving run or the shadow.
- It does not let an agent hold credentials or apply a change.
- It does not read or move your business records.
09FAQ
Five direct answers.
Write your app against the fusion.*/v1 contract rather than the model's own API. elan1 Run Substitution then replaces the component behind the contract in nine recorded steps, and your code keeps calling the same contract; the goal is no change to consumer code at all.
Two named people, at human gates H1 and H2. Substitution is never autonomous, and elan1 Run also asks elan1 Govern for a gate check at step 7.3 before the switch.
The substitution does not go ahead. A component that does not pass the K1–K7 suite cannot claim the contract, so the current component stays in place; rollback is its own trigger and takes the same nine steps.
Our target is inside 72 hours, with no change to consumer code. It is a target, not a published measurement.
Yes. Rollback is its own trigger and takes the same nine steps.
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 · SUBSTITUTION
Replace a component without rebuilding the integration.
Start with a paid 90-day pilot: your stack behind the contracts, and a substitution taken through all nine steps.