Attestation
Each boot comes with a statement that the Mac’s Darkbloom agent asserts with an Apple App Attest key: what runs (the qualified agent build, the image, kernel, and VM configuration, the egress policy) and the keys the guest generated, bound to the fresh nonce your CLI chose and to your SSH key, whose private half only you hold. Your CLI checks it against Apple’s App Attest root, the Darkbloom release key compiled into it (which signs the list of qualified builds), and Darkbloom’s build-revocation list, beforessh, vnc, codex, secret set, and the MCP
server’s sandbox_exec, and pins the host key the boot attests: your CLI
accepts no other host key for that boot. darkbloom-sandbox-cli attest sbx-…
prints what it attests.
Your connection
ssh, vnc, and codex traffic is encrypted end to end between your machine
and the attested guest: Darkbloom’s gateway relays it and cannot read it in
transit. The Mac’s owner controls the machine the guest runs on, so this is not
a claim of confidentiality from them. See what is not claimed
yet.
Your workspace
Your workspace is stored encrypted on the Mac. Its key is kept by Darkbloom and released, sealed to the boot’s attested key, only to an attested boot. Darkbloom can decrypt your workspace: do not keep anything there you would not trust Darkbloom with. The encryption does not detect tampering: the Mac’s owner could corrupt or roll back parts of it, and the sandbox would not notice.Secrets
Send a secret with:/run/secrets/NAME in the guest (on macOS, in its RAM disk at
/private/var/run/darkbloom-ram/secrets/NAME). The service carries them sealed
and does not open them.
A secret lasts one boot (it is sealed to that boot’s key): send it again after
each resume. Each is 1 byte to 64 KiB, at most 32 per sandbox.
What Darkbloom records
Darkbloom records:- account, sandbox, and Mac identifiers;
- sizes, platforms, states, and the reasons for them;
- timestamps, billed seconds, and charges;
- your SSH public key and the device name
loginregistered; - the hostnames you allow;
- the hostnames of connections the gateway refused;
- per-sandbox connection and byte counts at the gateway, kept per boot for 90 days, for abuse handling and any daily egress limit;
- the IP addresses your requests come from (access logs).

