Mission control · EGSE · RF links · GNSS simulation

Ground systems for space, from the bench to orbit.

Stellar Systems builds the software and hardware that integration labs, operators and subsystem manufacturers use to test, qualify and fly: mission control, bench interfaces, RF link emulation and GNSS simulation that share one set of procedures.

Pre-flight checks · flatsat-1 bench-1 · Stellar Link
SIM AIT IVV IN ORBIT
10:42:07.114 send obc.set_mode SAFE CAN · ECHO
10:42:07.958 expect obc.mode is SAFE ✓ 0.84 s
10:42:08.310 check eps.bus_voltage 28.1 V · 26–30 V
10:42:09.020 rf pass leo_doppler_v1 · UHF AOS · locked
10:42:11.021 ask operator: arm deployment? confirmed
10:42:14.487 step "Pre-flight checks" passed · evidence
Bus voltage 28.1 V
Link SNR 18.4 dB
Links bound 5 / 5
Products

Four products, one chain

Stellar Control runs the procedures, Stellar Bench reaches the hardware, Stellar Link brings the RF channel to the bench, Stellar GNSS puts the receiver in orbit.

Software · Mission control

Stellar Control

From the test bench to orbit, with the same procedures.

Drives your equipment under test, your EGSE and your spacecraft through telecommands, telemetry and file transfers. Catalogues, topologies and procedures are code: versioned, reviewed and validated before they reach a bench or a satellite.

  • Procedures as code, GitOps workflow
  • SIM, AIT, IVV and in-orbit rules
  • Evidence and reports for every run
Discover Stellar Control →
Hardware · EGSE

Stellar Bench

Every bus of your bench, one box.

Connects your equipment under test through CAN, RS-422, RS-485, Ethernet, SpaceWire and discrete I/O, and brings every link to Stellar Control over one network cable.

  • Stellar Control gateways built in
  • Plug it in, the bench joins the system
  • Same procedures from component to flatsat
Discover Stellar Bench →
Hardware · RF

Stellar Link

Fly the pass on the bench.

A software-defined radio test bench for satellite links: CCSDS and CSP over BPSK, QPSK and GMSK, a LEO pass played in the FPGA, measured assertions and a report for every run.

  • Doppler, path loss, AOS and LOS replayed
  • Profiles, scenarios and campaigns in YAML
  • Measured assertions, JSON reports
Discover Stellar Link →
Hardware · GNSS simulation

Stellar GNSS

Put your GNSS receiver in orbit, on the bench.

An RF GNSS constellation simulator built for space receivers rather than cars: scenarios as code, real-time control, injected offsets and truth data to judge every fix. Orbital dynamics and a closed loop with Stellar Control are on the roadmap.

  • GPS L1 C/A, 12 channels, RINEX ephemeris
  • Real-time API, injected position and clock offsets
  • Roadmap: LEO to GEO orbits, Stellar Control loop
Discover Stellar GNSS →
How it fits together

The procedure validated on the flatsat is the procedure flown

Only the topology changes between environments. Each one enforces its own rules, and every run leaves its evidence.

  1. Describe

    Catalogues, topologies and procedures in Git, reviewed and compiled in CI by Stellar Control.

  2. Simulate

    Deterministic simulated targets with faults, link losses and passes, on a laptop.

  3. Connect

    Stellar Bench binds CAN, serial, SpaceWire and Ethernet to the system in one box.

  4. Emulate RF

    Stellar Link replays the pass: Doppler, path loss, AOS and LOS, measured.

  5. Fly

    The same procedures in orbit, with confirmations, plans and a full audit trail.

Use cases

From the supplier's ICD to the test chamber

A payload to integrate, a CubeSat from simulation to flight model, a test bench that runs unattended: each one runs in your browser or in an environment of your own.

All Stellar Control use cases →

How we build

Engineered for traceability

Configuration as code

Everything that describes a mission lives in a repository, follows merge requests and is compiled before use.

Evidence by default

Every command, acknowledgement and verdict is recorded with the configuration version that produced it.

Your infrastructure

On-premise, in hosted isolated cells, or hybrid: the core where you want it, gateways next to the hardware.

Open contracts

Rust and Python SDKs, HTTP and WebSocket APIs, and a documented contract any language can join.

Get started

Bring your ICD. Run your first procedure.

We help you from the interface document to the first run on your bench.

  1. Write the catalogue of your platform or subsystem.
  2. Build its driver with the SDK, checked against test vectors.
  3. Run your first procedure on a simulated target.
  4. Connect your bench and run it for real.