Run confidential AI workloads. With cryptographic proof of execution. On any provider.
Apogee is the customer-side runtime for confidential AI compute. One SDK across every confidential-compute provider. Every workload returns a hybrid post-quantum signed receipt, verifiable offline by any examiner for ten years or more. GPU enclaves on the ground today. Orbital operators as their capacity reaches production.
Proof a provider cannot grant itself.
Provider-neutral by construction
Clouds attest to themselves; their proof lives and dies with your contract. Apogee's envelope is customer-held and verified against independently published keys; it survives a provider switch, an audit five years later, and the provider itself going away.
Cryptographic execution provenance
Every workload produces a hybrid Ed25519 plus NIST FIPS 204 ML-DSA-65 attestation envelope generated inside the provider's confidential-compute TEE: terrestrial GPU enclaves today, on-orbit TEEs as operators ship them. Verifiable offline by any third party for ten years or more.
One audit format across providers
One SDK and one audit format across confidential-compute providers and, as their capacity reaches production, orbital operators including Starcloud, Axiom Space, Orbital, and ODC.space. Your compliance posture does not depend on any single provider's stack.
The trust layer ships first. The scheduler arrives as the market does.
One confidential workload. Six steps. Signed end to end.
Submit workload through Apogee SDK
The customer submits an AI workload through the Apogee Runtime SDK with policy attached: latency budget, compliance tier, cost ceiling, and sovereignty constraints.
Policy engine selects the provider
Apogee's policy engine places the workload on a confidential-compute provider that satisfies the declared constraints: GovCloud GPU enclaves today; orbital operators such as Starcloud, Axiom Space, Orbital, and ODC.space as their capacity reaches production.
Bind to provider and deploy
The workload binds to the selected provider and deploys with sealed model weights, decrypted only inside the enclave. For orbital providers, uplink happens across ground-station visibility windows. Routing stays beneath the customer-facing SDK.
Execute inside the TEE
The workload runs inside the provider's confidential-compute trusted execution environment. Result, telemetry, and environmental measurements stay sealed inside the TEE until signing.
Generate attestation envelope
A hybrid Ed25519 plus NIST FIPS 204 ML-DSA-65 signature is generated inside the TEE, covering the workload result, telemetry, and environment. Post-quantum ready for CNSA 2.0 timelines.
Anchor to certificate-transparency log
The envelope hash is published to a public, append-only CT log. Any third party (auditor, regulator, customer) can verify the envelope offline for the next ten years, without contacting the provider or Apogee.
Building the customer-side runtime for confidential AI compute.
We are early. We are selective about who we work with. If you run regulated AI workloads, operate confidential-compute or orbital infrastructure, or invest in deep-tech infrastructure for the next decade, we would value a conversation.
Who we are talking to
- Compliance and ML platform leads running regulated AI workloads
- Confidential-compute providers and orbital operators (Starcloud, Axiom Space, Orbital, ODC.space)
- Defense-tech and deep-tech venture investors
- Engineers with TEE, confidential-compute, or post-quantum cryptography experience