Diagnose the past. Protect the next effect. Operate the boundary.
The open protocol is free. The one public pilot is $25K for 90 days and 1 protected workflow. Gate Qualification can carry accepted evaluation evidence into that decision when needed. It is not identity, certification, or authority. Implementation is scoped; Operated Gate is quoted only for a customer-specific deployment.
Qualification travels. Authorization stays local. Gate controls the consequence.
Build and verify under your own keys when your team wants to operate the trust boundary itself.
Protect one buyer-selected consequence boundary, beginning with synthetic and read-only validation before any accepted production change.
Turn the selected risk area into a fail-closed prospective control, with optional qualification and reliance-risk policy at the real executor boundary.
Operate policy, approval, consumption, reconciliation, and evidence inside one contracted deployment. Scoped after implementation acceptance; not a generally available live service.
No seat tax and no generic API-call bundle. Production pricing follows the number and risk of protected workflows, the deployment boundary, evidence retention, integrations, and service level. Run the free sandbox first →
Gate Qualification v2 is an open entry path, not a pricing or certification tier. It carries portable, time-bounded qualification from accepted evaluation evidence into a Gate implementation when the protected workflow requires evaluated-candidate evidence. Qualification is not authorization, certification, deployment evidence, or proof of a successful effect.
Reliance Risk Plane scope is also deployment-specific. EMILIA can verify customer-supplied loss terms, reserve declared open exposure, and emit bounded risk evidence. EMILIA does not insure, bear or allocate loss, adjudicate disputes or losses, prove coverage, causation, solvency, or population completeness, or move money. See the shipped boundary →
Protect one real consequence boundary in 90 days.
The first profile is finance operations vendor bank-detail change or payment release: no accepted exact-action authority and required evidence, no provider entry. Missing, stale, exhausted, invalid, or mismatched authority does not admit provider entry on a completely mediated covered path. Gate does not prove bank-detail correctness, payee identity, fraud absence, or provider success. Other consequential workflows remain eligible. Every pilot starts with synthetic and read-only validation, and no production path changes until the buyer accepts the executor-bound Gate design.
Protocol proves. Gate prevents.
Assurance is a service layer, not a proprietary verdict.
Verification remains open and reproducible. Paid engagements help teams operate repeatable re-performance, maintain conformance records and continuous evidence, and prepare bounded packages for auditors and underwriters. EMILIA does not issue audit opinions or accredited certifications.
Explore the Assurance Plane →One product, adapted to different consequence boundaries.
These profiles package action schemas, policy templates, and integration guidance around Gate. They are not separate products, and they do not by themselves establish legal compliance.
Evidence requirements for configured public-sector determinations and caseworker approvals.
Policy and evidence adapters for configured money-movement and treasury actions.
GRACE composes authorization evidence with action and measurement records at energy-control boundaries.
Distinct-human, initiator-excluded quorum evidence for actions that require more than one approval.
Start with one consequential workflow.
Begin with the canonical 90-day pilot, or use the open MCP path to protect one configured tool yourself.