-
Notifications
You must be signed in to change notification settings - Fork 0
Home
One-liner: SpaceComms is an open "universal language" that lets different satellite operators share collision alerts and maneuver plans, regardless of which systems they use.
Simple analogy: Imagine air-traffic control—pilots from any airline can communicate with any control tower because they all speak the same radio protocol. SpaceComms does the same for satellites: operators, tracking providers, and regulators can all exchange safety information using a common format, without being locked into one vendor's platform.
Space is getting crowded. Over 10,000 active satellites orbit Earth, with tens of thousands more planned. Every close approach between objects is a potential collision—and collisions create debris that threatens everything else in orbit.
Today's challenge:
- Satellite operators get collision warnings from different sources in different formats.
- There's no standard way for operators to share their planned maneuvers.
- Coordination happens through ad-hoc emails and phone calls.
- Each new tracking provider creates yet another proprietary system.
What's needed: A neutral, open protocol that any system can speak—not another closed platform, but the "common language" layer underneath all of them.
Phase 3 Complete — Ready for technical evaluation
| Feature | Status | Notes |
|---|---|---|
| 🛰️ CDM Exchange | ✅ Complete | CCSDS-aligned format, propagation, storage |
| 📊 Dashboard | ✅ Complete | Web UI with demo mode labels |
| 🔌 Adapters | ✅ Complete | Space-Track + Constellation Hub mocks |
| 📈 Observability | ✅ Complete |
/metrics endpoint, structured logging |
| 🔒 mTLS Security | ✅ Config ready | TLS configs, certs, secure demo script |
| 🔄 Version Negotiation | ✅ Complete | Protocol version in HELLO, compatibility rules |
| 🧪 Resilience Tests | ✅ Complete | Restart, malformed message, version mismatch |