Ship your product into Sovereign Mode.

You bring three artifacts. The pipeline returns an attested, contained deployment your buyer’s security team can verify without trusting you or Ember.

WHAT YOU BRING

• 1A digest-pinned container image. name@sha256:… only; a tag can move after review, a digest cannot.
• 2An env index card. The names of secrets and settings your image needs, never the values. They are read from your shell env at deploy and sealed.
• 3An egress manifest. The exact hostnames your product may reach, port 443 only. No wildcards, no IP literals.

The whole submission is one file, ember.json:

{
  "name": "acme-rag",
  "spec": {
    "image":     "ghcr.io/acme/rag@sha256:9f2c…",
    "env":       { "MODEL": "claude-sonnet-5" },
    "secretEnv": ["ANTHROPIC_API_KEY"],
    "egress":    [{ "host": "api.anthropic.com", "port": 443 }]
  }
}

WHAT THE PIPELINE DOES

The pipeline renders a contained deployment: your image runs in an attested confidential VM whose only network exit is a policy proxy, and your egress manifest is inlined into the deployment measurement. That measurement is approved on-chain by the governing smart contract account before anything boots. Secrets are sealed; silicon↔chain evidence is captured.

A config edit cannot widen your access. Any change to the image or egress list produces a new measurement, which requires a new on-chain approval.

THE WALKTHROUGH

Onboarding runs through the ember CLI, against an endpoint and vendor token issued at the briefing:

ember init                          # scaffold ember.json, the index card
ember deploy                        # secrets from your shell env, sealed
ember status                        # state + attestation evidence
ember egress add api.example.com    # a governed ceremony, not a config edit
ember release name@sha256:…         # a new version, the same ceremony
ember verify                        # quote + chain, trusting no one

When the buyer’s institution holds the governing account, ember release becomes propose → approve → commit: they review the diff, approve on-chain, and the pipeline commits on approval.

PROVE IT, DON’T PROMISE IT

ember verify fetches the live attestation quote, checks its signature against the silicon vendor’s published root of trust, and compares the measured deployment to the approved-measurement list on-chain, trusting neither your infrastructure nor Ember’s records.

The full method is in the technical whitepaper → If a CAIQ-style questionnaire is in your deal thread, we’ve answered it →