One engine for Earth-observation and telecom operators. Every maneuver scored by what it costs the whole mission — fuel, power, collision risk and ground contacts, together — not just delta-v. Free on one mission, metered API to build on, per-fleet in production.
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.
Same cross-impact engine on every plan — from one mission to a full EO or telecom constellation.
| Free | Developer | Operator | Enterprise | |
|---|---|---|---|---|
| Satellites / missions | 1 | 3 | Whole fleet | Unlimited |
| Cross-impact ranking | On demand | Via API | Continuous | Continuous |
| 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, not just delta-v. Free and Developer include a monthly allowance; Operator runs continuously across the fleet.
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 cross-impact ranking against 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.