Disclosures
Launched, and plain about it.
All four elan1 platforms are available. Here are the limits that still apply to every claim, price and example on this site, in plain words.
elan1's disclosures page states plainly what is launched, what each platform does not do, and the limits a buyer should plan around. All four platforms, elan1 Govern, Work, Decide and Run, are available, with L1 Guarded and L2 Attested; L3 Proven is event-gated on auditor acceptance.
01The plain facts
Six things to know before you read anything else.
elan1 Govern, elan1 Work, elan1 Decide and elan1 Run are available.
Every Work line, Govern level, Decide module and Run module on this site is available, from ELAN1 AGENTIC TECHNOLOGIES PRIVATE LIMITED. L3 Proven is reached only when an outside auditor accepts an L2 bundle in writing; it never carries a date.
Prices are list prices, exclusive of GST.
GST is added at the applicable rate on the invoice. Partner and OEM revenue shares are not published; they are partner terms on request.
We name no customers; no logos, testimonials, badges or awards.
Where other sites show a logo wall, we show the claims register, what comes next and specimens. A customer is named only with its written permission.
Every record, screen or code sample is an illustrative specimen.
Each carries the caption “Illustrative specimen. Not customer data.” The demo company, Kolam Components*, is fictional.
We hold no security or AI certifications.
Any we earn will be listed in the trust centre with the certificate. Using elan1 does not certify you against any framework.
No model sits in the allow path.
Where elan1 Work or elan1 Decide uses a model to draft, the product page names it in full. “Enforced” applies only in Mode A.
*Kolam Components is a fictional company; all data is illustrative.
02Known limits
What the product does not do, said once, here.
Each limit is also stated on the page it affects. None of those pages claims more than this list.
| Limit | What it means | Where it shows |
|---|---|---|
| Mode B cannot stop a write made around elan1 | It evaluates and records every write intent it is asked about. We never say “enforced” for Mode B. | What we claim |
| An L1 record is tamper-evident to you, not signed | Signing and offline checking are L2 Attested. | Verify a record |
| DPDP erasure and an append-only chain | The record holds a payload hash, never the payload. Whether a hash and a record identifier are personal data in your context is for your counsel. | India DPDP Act |
| Product names are subject to trademark clearance | Names may change if clearance requires it. Any change is logged here. | Earlier names |
03Earlier names
What we used to call things.
If you read an earlier note or deck, this is how its names map to the names on this site.
| Earlier name | Now |
|---|---|
| The elan1 kernel / the elan1 layer | elan1 Govern |
| Earlier working names for the work layer and the small-firm product (retired 6 Oct 2026) | elan1 Work · “elan1 Work for small firms” |
| Earlier working name for the runtime (retired 6 Oct 2026) | elan1 Run |
One public name per layer: elan1 Govern, elan1 Work, elan1 Decide and elan1 Run. “Platform” is a navigation label; in body copy we say “layer”.
04Versioned policies
Every policy page has a version, and every change a redline.
Deletions are struck in ink. Additions are underlined in kiln. The same pattern applies to the declarations your rules live in.
| Page | Version | Effective |
|---|---|---|
| What we claim | v1.3 | 10 Oct 2026 |
| What's next | v2.0 | 10 Oct 2026 |
| Disclosures | v1.1 | 10 Oct 2026 |
| Security | v1.1 | 10 Oct 2026 |
| Pricing | Current list prices | 10 Oct 2026 |
| Regulation hubs (EU AI Act, ISO/IEC 42001, NIST AI RMF, India DPDP Act) | v1.1 | 10 Oct 2026 |
Redline example: a declaration, version 3 against version 4
A declaration holds a process’s rules. When it changes, both versions stay readable side by side, and every proof record names the version that was in force.
decl_gst_purchase · version 3 and version 4- 1.1Scope: purchase invoices posted to the books of Kolam Components*.
- 2.3A purchase invoice above
₹5,00,000is held for the finance head. - 2.4
An invoice from a new vendor may post at autonomy level A2. - 3.1The GST gate (G4) refuses a rate mismatch with a typed code.
- 4.2Autonomy ceiling:
A3.
- 1.1Scope: purchase invoices and vendor payments posted to the books of Kolam Components*.
- 2.3A purchase invoice above ₹2,00,000 is held for the finance head.
- 2.4An invoice from a vendor added in the last 30 days is held for a named approver, at any amount.
- 3.1The GST gate (G4) refuses a rate mismatch with a typed code.
- 4.2Autonomy ceiling: A2. Above it, a person decides.
05Versions
What changed in these disclosures.
What changed
- 10 Oct 2026v1.1
Launch: the plain facts now say all four platforms are available and prices are exclusive of GST. Open questions became known limits; partner revenue shares are partner terms on request.
Owner decision, 10 Oct 2026: all four platforms launched.
- 6 Oct 2026v1.0
Disclosures published: six plain facts, three open questions, earlier names and the versioned-policy list.
First public version.
- 6 Oct 2026v1.0
Earlier working names for the work layer and the runtime retired; elan1 Work and elan1 Run are the only public names.
Founder decision.
When a claim, a level or a price changes, the change is logged here with the reason. Earlier versions stay readable; history is never edited in place.
// DISCLOSURES
Ask us what isn't on this page.
If a limit matters to your review and we have not written it down, we would rather hear it now.