One shared MissionLab core

Professional Digital Twin

Design, configure, predict, run, inspect, compare and export mission evidence using accepted, versioned model owners and explicit provenance. The same core supports education and Challenge without a separate physics fork.

Software-runnable for structured pilots; remaining validation is disclosed on the offer page

Software-runnable for structured engineering evaluation pilots. Educator classroom validation, generic Mission Studio execution composition, and measured hardware correlation remain open.

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 a separate, supervised hardware product. 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 missions can be completed in software. Supervised hardware can add measured evidence after separate correlation and 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