Coordinated maneuver decisions between operators.

When two operators face a conjunction, avoiding a collision becomes a coordination problem. OKAPI:Platform streamlines collision avoidance between active satellites on one shared, event-driven platform, so you resolve the event with agreement, not guesswork, and manage one or many satellites without constant oversight.

Developed with ESAGuest access for any partnerAll in one platform
The coordination problem

The maneuver is the easy part. Agreeing on it is not.

When two operators face the same conjunction, the hard part is not the burn. It is agreeing who moves, reaching the right person before TCA, and working from the same picture when the data lives in separate inboxes. Watch the same event play out both ways.

OKAPI SAT 3vsGuest 3Non-critical
46h to TCA
T+2h
CSpOC new CDM.
Non-critical
Illustrative coordination timeline, not real screening data
Verdict
Coordinating

Tracking the event as new data messages arrive.

First CDMT minus 24hTCA

This is an illustrative coordination timeline built to demonstrate the workflow. It does not represent real conjunction screening data.

One platform, from first alert to executed maneuver

Everything the conjunction needs, in one place.

From the first alert to the executed maneuver, both operators work the event on one platform, from one timeline.

Data sharing

Event-driven data sharing

Both operators see the same synchronized timeline, with critical conjunctions, secondary operator details and key facts in one view. CDMs are regenerated from both sides, so nobody argues about whose data is right.

Interoperability

Coordinate with any partner

Guest access lets you bring in any operator, and their contact details live in the platform, so the right person is reachable before TCA instead of after it.

Protocols

Protocols that carry forward

Agree who maneuvers once, and the protocol applies automatically to every future event with that operator. Start from the Space Safety Coalition best practices, share a protocol for others to adopt, or set a protocol between two operators.

Accountability

One event summary

Every message, plan and decision from the event lands in a single auditable timeline, exportable as an event summary once it closes.

Who it serves

Built for anyone who has to share the orbit.

Satellite operators

Resolve a conjunction with agreement, not guesswork.

Book a demo
Operations readiness check

Ten questions. Then you know where coordination is exposed.

Ten questions across live operations, from first contact after deployment to agreeing who moves. Answer for the fleet you fly today. Nothing is stored and nothing is sent.

Ten questions, one at a time

How much of your operations day is already covered?

Each question is one thing OKAPI:Astrolabe handles. Answer yes, partly, or not yet, and skip anything you are unsure of. Nothing is stored and nothing is sent.

Handle the conjunction from start to end

Coordinate your next close approach in one place.

Bring a live event or a recent coordination question and we will walk through it together.