What powers MissionLab

Professional Digital Twin

The Digital Twin is the engineering core behind MissionLab’s spacecraft missions. Design, configure, predict, run, inspect, compare and export mission evidence using validated model owners and explicit provenance. The same core supports education and Challenge without a separate physics fork.

Pilot-ready

Current maturity

The software workspace is runnable now. It exposes model identity, version, fidelity, calibration, validation and channel provenance independently rather than inventing a single whole-spacecraft fidelity label.

KidSAT is optional supervised MissionLab hardware. Its Windows COM-port workflow exists, while formal simulation-versus-measurement correlation remains a physical commissioning gate. Public remote hardware control is not offered.

Capability inside the Twin

Mission Control

Mission Control turns model runs into an engineering operating surface: mission state, telemetry, events, comparisons and evidence. It is not a separate customer-facing product.

Bounded developer access

Local/private Developer API

The versioned cubestem.dt-core.developer.v1@1.0.0 API and TypeScript, Python and Jupyter source clients support explicitly enabled local/private evaluation. They are not a stable production-public or browser API, do not host arbitrary code or bring-your-own models, and grant no hardware or official authority.

Software first; hardware optional

MissionLab and the Digital Twin are complete without hardware. Supervised physical experimentation can add measured evidence after separate acceptance.
Optional hardware overview

Schools and institutions

Pilot conversations and demos are coordinated through operator-provided contact—simulator-first scope, honest hardware boundaries, no embedded CRM on this site.
Contact & next steps