Skip to content

Development Roadmap

Same plan as the product roadmap on stellor.space

This page stays in Release notes, above each evaluation build. It is the forward plan. A version page (Beta 0.1.0, and later 0.1.1, 0.2.0, …) says what that build ships.

Public columns: Product Roadmap.

Q3 – Q4 2026 — Beta Evaluation Build 0.1.0

What this window opens. Depth is on Beta 0.1.0.

  • ASTROLAB Web public release
  • Open Trial access and licensing rollout
  • Server capacity scaled to user demand
  • Custom agreements with Enterprise (proof of concept)
  • Space Situational Awareness Modules
  • Propulsion Subsystem & Trajectory Design Modules Integration
  • Opening of the Basic plan

Space Situational Awareness Modules

The manoeuvre layer these modules add:

  • Collision avoidance. Δv to avoid a conjunction.
  • Disposal. Manoeuvres for the usual end-of-life cases: a controlled deorbit, a raise into a graveyard orbit, and the other disposal burns a mission actually flies.
  • Re-entry. A simulation of the re-entry itself, past the uncontrolled decay already in Lifetime.

Propulsion Subsystem & Trajectory Design Modules Integration

  • Multi-attitude segments. Attitude can change along a segment. Propagation is event-based: the arc runs until an event (eclipse, target acquisition, burn start or stop, and similar triggers) and the next attitude takes over.
  • Higher-fidelity station keeping. The analytical budget in Beta 0.1.0 stays. The next cut ties station keeping to the propulsion subsystem — thrust, tank, and propellant — instead of a Δv envelope on its own. See Station keeping.
  • Orbit raising. Manoeuvre design for Earth orbit raising (EOR).
  • Interplanetary transfers. Manoeuvres toward the Sun–Earth libration points (L1, L2) and similar interplanetary legs.

2027+ — Scale & Depth

  • Python scripting API for Monte Carlo studies and batch runs.
  • Analysis extension through S/C operational modes. A sequence of spacecraft modes. Each mode carries an attitude, a power draw, and a propulsion state, and that sequence feeds the trajectory and the analyses.
  • Higher-fidelity subsystem models. Thermal, power, and propulsion past the first cuts in 0.1.0.
  • Real hardware equipment presets. Catalogues of antennas, sensors, and bus hardware a mission can drop in.
  • Automated report generation. A finished run writes the report, instead of assembling charts by hand in the dashboard.
  • Enterprise collaboration and integrations. Shared missions across a team, and links to the tools an enterprise already runs.