Run AI workloads in orbit. With cryptographic proof of execution. Across every operator.
Apogee is the customer-side runtime for orbital compute. Every workload Apogee schedules produces a signed, post-quantum attestation envelope generated inside the satellite's secure chip, verifiable offline for the full ten-year mission lifecycle.
A runtime built for what no operator-side stack can deliver.
Customer-neutral by construction
Apogee is the only runtime built customer-side rather than operator-side. NVIDIA cannot be neutral; they sell hardware to every operator. The operators cannot be neutral; they compete with each other. Apogee is the only credible neutral path.
Cryptographic execution provenance
Every workload produces a hybrid Ed25519 plus NIST FIPS 204 ML-DSA-65 attestation envelope generated inside the satellite's on-orbit confidential-compute TEE. Verifiable offline by any third party for the full ten-year mission retention window.
Cross-operator workload portability
One SDK, one billing relationship, one audit format across Starcloud, Axiom Space, Orbital, and ODC.space. Workloads migrate between operators automatically when capacity shifts. Mission continuity does not depend on any single operator.
Four components on one substrate, shipping over eighteen months.
One orbital 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.
Scheduler bids across operators
Apogee's scheduler bids the workload across Starcloud, Axiom Space, Orbital, and ODC.space using forecasted capacity, pricing, latency, and orbital availability for each operator's fleet.
Bind to operator and uplink
The workload binds to the selected operator and uplinks to the target satellite during the next ground station visibility window. Operator routing happens beneath the customer-facing SDK.
Execute inside the on-orbit TEE
The workload runs inside the satellite'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 on downlink. Any third party (auditor, regulator, customer) can verify the envelope offline for the next ten years, without contacting the operator.
Building the customer-side runtime for orbital compute.
We are early. We are selective about who we work with. If you operate orbital infrastructure, lead defense or AI lab business development, or invest in deep-tech infrastructure for the next decade, we would value a conversation.
Who we are talking to
- Defense and AI lab BD leads on orbital compute
- Orbital operators (Starcloud, Axiom Space, Orbital, ODC.space)
- Defense-tech and deep-tech venture investors
- Engineers with on-orbit compute or post-quantum cryptography experience