BRIEFING
A 30-minute technical session with our team: how Sovereign Mode enforces ZOA in your product, what your client’s security review will require, and what a pilot involves.
WHAT YOUR REVIEWER WILL CHECK
Pull the attestation document. Every published deployment exposes one.
Hash the measured workload it carries.
Compare that hash to the approval record your client holds on the blockchain — the read is your own.
# hash the measured workload; compare it with the allowlist on the blockchain
ember verify --app <approval contract address> --quote <quote file or URL>
COMMON QUESTIONS
No. Package the application you already ship as a digest-pinned container. The product experience your clients see stays the same.
No. Sovereign Mode invokes the models you already use. The inference provider receives prompts and completions under the credential and terms your client approved.
For one reason: it holds an approval record neither the vendor nor Ember can quietly edit. There is no token. Your client’s key is a passkey — one tap.
Pilot terms are part of the briefing. The shape is fixed: metered attested compute, no take rate on inference, priced as a tier of your product.