DEVELOPERS
Package the application you already ship — retrieval, agents, inference — propose it to your customer, and go live in a hardware-isolated workload. Everything here is the vendor engineer’s path.
WHERE ZOA IS REQUIRED
Attorney–client privileged material that cannot be disclosed to the software vendor.
PHI where the vendor cannot or will not become the processor or business associate.
Classified or export-controlled information.
Data whose disclosure would waive privilege or violate customer commitments.
Cross-company learning where neither contributor can reveal data to the other.
Workloads where the operator must be excluded technically, not contractually.
IP where even administrators and support personnel must sit outside the trust boundary.
The common property: disclosure to the operator is not an option. Zero operator access is that property, made checkable.
GET RUNNING
01 · PACKAGE
ember init
Describe the app you already ship: pinned image, secret names, egress.
02 · GO LIVE
ember deploy
Secrets sealed, egress measured, an attested HTTPS endpoint — and a live trust page.
03 · VERIFY
ember verify
The measured workload checked against the blockchain approval record.
DOCUMENTATION
pl pipeline path, plus an installable agent skill.
Attestation & verification
What the quote contains, how measurements are checked, what your customer’s reviewer runs.
Technical whitepaper
The full design — measurement, attestation, governance, and the limits of each claim.
# start locally — no account, no key
npm install -g @ember-sovereignty/provisioner && ember init