Show HN: First API for orbital compute scheduling with real physics
2 points
1 hour ago
| 1 comment
| rotastellar.com
| HN
subhadipmitra
1 hour ago
[-]
Hi HN - we built an API that takes a satellite ID and a workload and returns a physically-accurate execution plan for splitting compute between space and ground.

The motivation: satellites generate ~1 TB/day but can only downlink ~7.5 GB per pass. As on-board compute improves, you need a planner that decides what runs where, schedules transfers across real ground station passes, and handles FEC/encryption overhead.

The planner runs full SGP4 propagation (same algorithm NORAD uses), computes eclipse windows, predicts passes for 12 ground stations with elevation-dependent link budgets, and produces deterministic plans.

You can try it live — our tracker lets you run plans against any satellite: https://rotastellar.com/tracker/ (select a satellite → Schedule tab → pick a preset → Plan Execution)

Happy to discuss the orbital mechanics, the placement heuristics, or anything else.

reply