Releases

2025

April 15

• Improved UX for conjunctions page: faster load times, and more visual indicators when data is loaded in the background.

April 3

• New dashboard page: The dashboard page now provides a summary of the next upcoming events, unread chat messages, and an overview of the responsibility distribution in existing coordination cases. The idea is to provide you with only those information that require your attention. You can then switch to the Conjunctions tab with the full timeline and event table if you want to look into everything in more detail.

March 5

• We simplified the notification settings to make them more intuitive.

February 25

• Clearly showing when an organization is connected as external service.
• Possibility to monitor only a defined set of satellites.
• More intuitive grouping of endpoints in the API specification.

February 13

• Starlink integration: If your satellites are in the same orbital region as the Starlink satellites, you can configure OKAPI:Astrolabe to send uploaded ephemerides to Starlink, in order to get fast, up-to-date screening against their whole constellation.

February 12

• Chat message notifications: Email notifications were extended, so you can configure to receive an email every time another operator sends you a chat message.

February 7

• Python SDK: We now provide a lightweight SDK for working with the OKAPI:Astrolabe API in Python.

• Note on non-maneuverable objects: If the secondary object is not maneuverable according to the CDM, you see a note about this in the event summary and in the case assignment ticket.

January 16

• Additional API endpoints for downloading and uploading data independent of a specific conjunction event, as well as new access management after phasing out the early adopters program.

2024

November 04

• Bilateral protcols: In addition to pre-defined baseline protocols, you can now define your own protocols and use them in bilateral agreements with other operators.

• Guest users: If you have conjunctions with operators that are not registered Astrolabe users, you can invite them as guest users. This means they can sign up for free and use basic functionality they need to coordinate with you.

October 02

• OPM and NDM support: The supported formats for ephemerides and maneuver plans now include OPMs and NDMs.

September 20

• Data sharing: In the updates table on the case page, you can now download CDMs, ephemerides and maneuver plans, to inspect the data. Ephemerides and maneuver plans are only accessible if they are your own or the operator who uploaded them agrees to share them with you. To configure with whom you want to share which data, you find a “Data Sharing” section on the settings page.

• Report generation: The case page includes a new button “Generate PDF report”. This will generate a summary of the conjunction event and everything that has happened in it so far.

• Baseline protocols: Last but not least, Astrolabe offers the first two protocols ready for use, implementing “rules of the road” based on best practices by the Space Safety Coalition. You find them in the protocols tab and can simply subscribe to use them. Protocols automate the initial case assignment proposal, if both operators are subscribed and the protocols apply to the conjunction event in question. Note that in order to be evaluated, they require some satellite information.

  The documentation includes more background and details on protocols. Feel free to get in touch in case you have questions or want a demo. Otherwise don’t worry, there will be more communication and features around protocols in the near future, including the possibility to create your own ones.

August 01

• Configure risk assessment thresholds: The Settings page was extended so that the owner of an organization can change the miss distance and collision probability thresholds used for categorizing a conjunction as “critical”, “observe”, or “non-critical”.

• Users can also change the deadline of individual action tickets, in case our proposed deadlines do not align well with your operational practice.

July 24

• Maneuver plan actions: Operators who accept a case assignment now get additional actions that allow them to upload tentative maneuver plans as OEMs (up to 10 per case), select which of those they commit to, then confirm the execution of the maneuver, and eventually validate that it was successful in avoiding the collision.

July 11

• Usability improvements: The action tickets in the “Done” column now contain information on which action by what user or organization closed the ticket.

  The bubbles in the Dashboard timeline are now linked to the conjunction event, so you can simply click on them to get to the conjunction page. Also the rows in the conjunction event table can be clicked.

  And the notifications now contain a link to the case. Email notifications about new cases also include information on whether the other operator is registered in Astrolabe (and thus available for coordination) or not.

June 10

• Improved “Updates” tab: In the “Updates” tab, both the table and the timeline now include not only CDM updates but also operator actions (like uploading ephemeris and accepting or rejecting case assignment). In addition, the table setup was improved; for example we distinguish now between “update time” (when an update entered the system) and “creation time” (when the received document was actually created).

May 13

• Ephemeris upload: Users now get “Upload ephemeris” tickets, through which they can upload OEMs. The OEMs are validated and then pushed to OKAPI:Aether for conjunction assessment. OKAPI:Aether creates new CDMs from the resulting risk estimations, which reach Astrolabe with the next batch of fetched CDMs.