A
The claims register
26 claims, each with its level, mode, status and the date it changed. Filter it, print it or copy it as text.
Open the registerTrust & evidence
What we claim and what we don't, how the system is secured, how a proof record is checked, what comes next and our disclosures. Every claim carries its level.
elan1's trust centre lists every claim the company makes and the assurance level at which it becomes true. It covers the claims register, security and data residency in India, launch disclosures, the roadmap, and how to verify a proof record yourself, so a buyer or auditor can check each statement rather than take it on trust.
01Today
Status is always written out. Colour only repeats it. L1 and L2 are available; L3 is reached when an outside auditor accepts an L2 bundle in writing.
| Claim | Level | Status (in words, never colour alone) |
|---|---|---|
| Tamper-evident proof record | L1 · Guarded | AvailableHash-chained, tamper-evident to you |
| Signed, checkable offline | L2 · Attested | AvailableEd25519-signed, checked with the free offline verifier |
| L3 Proven | L3 · Proven | On auditor acceptanceAn outside auditor accepts an L2 bundle in writing |
| Certificates · Customer logos | No level | True todayNone held · none shown |
02Trust centre
Each page carries a version, an effective date and a log of what changed. Nothing here is gated.
For security reviews
Procurement and CISO teams usually read Claims, Security and Verify in that order, then ask for the security review pack.
03In place of a logo wall
No customer logos, testimonials, analyst badges or awards. Instead: the register, what comes next and the evidence object itself.
A
26 claims, each with its level, mode, status and the date it changed. Filter it, print it or copy it as text.
Open the registerB
Future improvements to the four platforms, in order, without dates. When the order changes, the log says why.
Read what’s nextC
Illustrative proof records, approvals and refusals, explained field by field, with the chain you can recompute yourself.
See the specimensStatus
Service status, component by component.
Each platform is listed on its own, so one layer’s status is never averaged with another’s. Security reports go to elango@elan1.ai.
04Versions
Every change is logged with its reason.
Launch: elan1 Govern, elan1 Work, elan1 Decide and elan1 Run available. Claims register v1.3; the roadmap became “What’s next”; security now states our role under the DPDP Act and the company contacts.
Owner decision, 10 Oct 2026.
Trust centre published: claims register, security, verification, roadmap and disclosures.
First public version.
Layer names fixed across every trust page: elan1 Govern, elan1 Work, elan1 Decide and elan1 Run.
Founder decision; see Disclosures for earlier names.
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.
// SECURITY REVIEW
Then ask the hard questions. A person replies within 2 working days, with the evidence.