One engine for Earth-observation and telecom operators — every maneuver scored by what it really costs the whole mission, not just delta-v.
Same engine on every plan. What changes is how far you can act on it — always with a human in the loop.
Self-serve billing is rolling out — for now every plan starts with a short access request, so we can match you to the right setup. Prices shown are starting points; final pricing depends on fleet size and usage.
From one mission to a full constellation.
| Free | Developer | Operator | Enterprise | |
|---|---|---|---|---|
| Satellites / missions | 1 | 3 | Whole fleet | Unlimited |
| Cross-impact ranking | On demand | Via API | Continuous | Continuous |
| Decision authority | See risk | Build via API | Approve & export OPM | + Autonomy dial |
| Mission-control console | Read-only | ✓ | ✓ | ✓ |
| REST API access | — | ✓ | ✓ | ✓ |
| Orbital-datacenter scheduling | — | — | Add-on | ✓ |
| Support | Community | Business hours | Dedicated | |
| SLA | Best-effort | Best-effort | Standard | Custom |
| Data residency / SSO | — | — | — | ✓ |
One scenario scored end to end — a maneuver, slew or schedule change, ranked by its whole-mission cost. Free and Developer include a monthly allowance; Operator runs continuously.
You send your orbital elements and any constraints. Apsia adds live space-weather and public tracking data, then returns ranked options you can act on.
Yes — one mission, capped monthly runs, no card. Test it on your own operations and decide on the numbers.
When compute moves to orbit, Apsia will schedule workloads against power, thermal limits and collision risk together — the same cross-impact reasoning we run for satellites today. It's an add-on for Operator plans and built in for Enterprise.