EMBER SOVEREIGNTY SYSTEMS

Check your email — click the sign-in link, or enter the code from it here:

USE AN AGENT / API CREDENTIAL

You're in. One more step: register your security key (a passkey). Signing in stays email-only — the key is what approves security-critical actions, as the owner of your org's smart account.

EMBER
SOVEREIGNTY
SYSTEMS

CONTROL VENUE KEYS RECEIPTS TENANTS USAGE
Add a security key to sign off on security-critical actions — loosening policy, owner changes. Email gets you in; the key approves.
EMAIL SIGN-IN (#2). The emailed link (or its code) gets you into the app. Add a security key (passkey) to sign off on security-critical actions — it's the owner of your org's smart account. Solo starts at 1 of 1.

00CONTROL

Who controls this org right now

One structure, always: the smart account governs, policy sets the dial, sealed keys execute only inside the attested TEE, and every call proves itself.

Smart accountGOVERNANCE · ALWAYS PRESENTMATERIALIZES WHEN YOU ADD A SECURITY KEY
The org's account. Solo starts at 1 of 1; teams hold n of m. Loosening policy takes the owner quorum, verified in-enclave. Never Ember.
PolicyTHE ROUTING DIAL · FAIL-CLOSED
allow-set: —
Attested executionWHERE SEALED KEYS OPENCID-PINNED
API keys are sealed to the blockchain-attested TEE and open only inside attested execution. The session signer signs receipts in-enclave and never governs. This layer is structural, not optional.
ReceiptsRECEIPTS · —
Every call signed in-enclave and verified against the registry-resolved signer. Refusals are receipted too.

01POSTURE · LAST — CALLS

CALLS
–
COMPUTE-SECONDS
–
METERED · $0.01/S
–
RECEIPTS VERIFIED
–
REFUSALS RECEIPTED
–
refusals land as receipts too

02VENUE KEYS

Sealed in the blockchain-attested TEE

Only attested execution opens a key. Sealing a venue again rotates the old key out in place; revocation fails closed. Rotation and revocation move under owner quorum when #2 lands.

— SEALED

02.1AGENT KEYS

Leashed credentials for harnesses

An ek_ key resolves to the AGENT role: it calls models under your policy and can never seal, revoke, or govern. The secret is shown once, at mint.

NAMEPREFIXMINTEDLAST USED

03RECEIPTS

Signed inside the TEE, per call

A receipt is trusted only when every bond holds: signer, venue, request, response, nonce, org, key, status. Open a row for the proof. Refusals are receipted too.

TIMEMODELVENUEVERDICTSTATUSSECPROOF

04TENANTS · SOVEREIGN MODE

One org per customer

Each customer gets the same control plane you use: their own owner set, the TEE signer on it, their own sealed keys and receipts. You provision the control object and route calls through it; you never hold their keys and cannot loosen their policy. Vendor-administered until claimed (#9); co-branded by default, white-label is a paid feature.

PROVISIONING · #9
Each tenant is its own org — its own owner set, sealed keys, and receipts — provisioned by your backend with the Ember SDK, never through this console's identity. The vendor-side ceremony and the customer's claim of governance land with #9; this view takes real data then (#14).

05USAGE

Metered on attested compute

$0.01 per compute-second of attested execution. Token counts ride along in receipts; the meter is seconds.

$0.01 / COMPUTE-SECOND
COMPUTE-SECONDS
–
METERED
–
PEAK DAY
–
REFUSALS
–
14-DAY COMPUTE
KEYLABELCALLSCOMPUTE-SECMETERED

POINT YOUR HARNESS

One env var. Any Anthropic-wire harness. OpenAI-compatible route is #4.


  


  
CLAIMS FOLLOW THE RECEIPT: keys custodied in an attested TEE, routing policy-enforced, every call receipted. Nothing above that rung. Humans hold governance at n-of-m; the TEE key signs only under their policy.