Kubernetes for Earth and orbit.
Where should this workload run? When? At what fidelity? The Orbit Scheduler makes placement decisions from real orbital mechanics, energy availability, and link windows - and lays the result on a timeline that survives eclipse.
Watch it place a workload across one orbit.
The scheduler fits each step where power and contact windows coincide, defers what it can't place, and pauses through eclipse - no steps lost, no data lost.
Placement is a physics problem now.
A terrestrial scheduler asks only where there's capacity. In orbit, capacity moves: power follows the sun, the link opens and closes on a schedule, and the satellite is somewhere new every minute. The Orbit Scheduler treats those as first-class inputs instead of exceptions.
Orbit-aware by construction.
Place against the orbit
Decide on-satellite, ground, or deferred from illumination, geometry, and the workload's compute and I/O needs.
Schedule to the power budget
Lay steps onto the timeline where available power covers them, deferring the rest to the next sunlit pass.
Route for the SLA
Choose ground, orbital, or hybrid execution to meet a latency target across LEO, GEO, and inter-satellite hops.
Hand off before the link drops
Anticipate contact and eclipse boundaries so work moves or pauses before connectivity does.
Put your first workload in orbit.
Tell us what you want to run and the satellite you want to run it on. We'll come back with a feasible plan - or an honest reason it can't be done yet.