EnfinitOSEnfinitOS
Developers

Build governed execution into every screen you ship.

28 SDKs across every substrate EnfinitOS governs — DOOH, CTV, mobile, AR / glasses / HUD / volumetric / hologram, gaming, automotive, smart home, wearables, audio, messaging, robotics, drone, satellite, aviation, maritime. The auditor / verifier trio is open source under MIT — no operator has to trust EnfinitOS as a vendor to verify the proof we issue.

28
SDKs published
24
Substrates covered
15
Languages
MIT
Open-source verifier
How to read this page

Three honest signals on every SDK card

We label every SDK with its real shipping status so you do not find out the hard way. Substrate readiness is tracked openly in the public readiness matrix, separately from the per-SDK status shown below.

Open source · MIT

Published on GitHub. The auditor / verifier trio lives in public so any operator, regulator, court, or third-party compliance tool can fork it, fuzz it, and verify our proof packs without trusting us.

Production-ready scaffold

Typed, tested, documented, and grounded in the 2026 platform reality (App Tracking Transparency, Matter 1.4, App Intents, Privacy Sandbox, ASTM F3411-22a Remote ID, IAB Gaming SIG viewability). Awaiting first customer-integration validation.

Alpha

Design + skeleton complete with adapter wiring. Vendor-side endpoints and operational hardening are tracked openly in the README. Reach out before relying on these in production.

EnfinitOS Governance Copilot

Deterministic execution. AI-assisted intelligence. Human-approved governance.

The rights gate, policy engine, proof issuance, metering, and settlement remain fully deterministic — every decision is signed, reproducible, and reconcilable. The Copilot layer sits on top of that evidence and translates it into operator-readable explanations, anomaly summaries, and draft proposals. The deterministic engine still decides; the Copilot only assists.

Every Copilot call is grounded in the underlying audit-log entry, logged through the platform's Observability layer, and reconcilable byte-for-byte from the evidence hash. We follow the NIST AI Risk Management Framework and the EU AI Act human-in-the-loop posture by construction — not by retrofit.

Phase 1 · live

Why was this blocked? Plain-English explanation of any deterministic refusal — a suspended right, a rejected offer, an upheld challenge. Starter tier gets a metered preview; Growth+ unlimited.

Anomaly summary. Operator-readable narrative over the recent event stream — revoke storms, offer rejection clusters, zero-delivery windows. Classical-ML detects; AI translates. Growth+ tier.

Phase 2 · roadmapped

Proof pack summarisation. Policy drafting from plain English. Operator Copilot for natural-language audit queries. Lands once Phase 1 has operator feedback shaping the prompts.

Phase 3 · scaffolded

Reconciliation explanation, SDK developer assistant, delivery risk prediction. Year-two: contract ingestion, reconciliation proposals, brand / auditor copilot. Reserved for Scale + Enterprise tiers — see the discovery surface at /v1/ai/features.

Try the Copilot · live demo

Pick a scenario. See the deterministic evidence + the AI explanation side-by-side.

No signup required. The demo uses canned audit-log evidence so you can see the shape; signed-in developers run the same Copilot against their own tenant via POST /api/v1/ai/explain-block.

Rate-limited to 3 calls per hour per IP. Sign up to run unlimited calls against your own audit log.
SDK catalog

28 SDKs · 8 categories · 15 languages

Every render SDK composes the substrate-agnostic Renderer Core — composition, not inheritance. Drone composes Robotics, not the other way round. Adapter-mostly SDKs (Satellite, Aviation, Maritime) translate vendor vocabulary into the EnfinitOS plane rather than wrapping native UI.

Renderer core

The substrate-agnostic foundation every render SDK wraps. Owns the rights / policy / proof plane; substrate-specific SDKs compose it, they do not inherit from it.

API reference

The HTTP API behind every SDK

All 28 SDKs are thin clients over the same governed HTTP surface — rights, offers, challenges, proof, metering, settlement, consent, drills, audit export. The full OpenAPI 3.1 spec is published; the live reference page is generated from the same spec the platform validates against.

  • OpenAPI 3.1 schema, single source of truth
  • Try-it-out in browser against a sandboxed tenant
  • Code samples in TypeScript, Python, Go, Java, Ruby, Rust
Sandbox · live

A real sandbox you can run a contract through

A scoped tenant, real rights handshake, real signed proof chain, and an in-browser auditor — running now in your browser tab. The sandbox issues packs in the same envelope.v1 format the production platform uses; every signature, every chain link, every metering projection is the real thing.

  • Provision a tenant in one click
  • Watch synthetic delivery events seal into the chain
  • Verify Ed25519 signatures locally — no server trust required
Trust model

Don't trust us. Verify.

The auditor / verifier trio is open source under MIT so any regulator, auditor, court, or compliance tool can verify EnfinitOS proof packs without taking the vendor's word for any of it. Ed25519 signatures over canonical JSON; SHA-256 hash chain; metering re-projected from the same source events the platform settles against.

Signed

Every proof pack is signed by EnfinitOS with a long-lived Ed25519 key whose public half is published. Tamper with any byte and the signature fails.

Chained

Each proof pack references the SHA-256 hash of the previous one for the same tenant. Drop one and the chain breaks visibly. The verifier walks the chain end to end.

Re-projected

The verifier re-projects metering from the same source events the platform settles against and re-runs settlement reconciliation. Output is bit-identical or the pack fails.

Reach the team

Get in front of an engineer, not a sales rep

Integration support, sandbox access, security disclosures, and partnership questions all reach the engineering team directly.

Sandbox access

Hosted sandbox in Q4 2026. Request an invite to be on the early-access list.

Security disclosures

Email [email protected]. GPG key + scope are published in our security.txt.