Curated software evaluation
Explore a bounded engineering question through curated software models and scenarios. Run, inspect, compare and export simulated mission evidence with model identity, provenance and limitations visible.
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.
Public software examples open without an account. Mission Studio asks you to sign in because missions, revisions and evidence belong to an organization.
Buyer summary · Print or save this page
For research laboratories and engineering teams evaluating current Digital Twin capability through declared design and mission trade questions. The evaluation supports evidence-backed discussion of supported models, not a qualification decision.
Choose a curated example or supported subsystem workbench, run a deterministic software case, inspect model version and channel provenance, compare or replay where supported, and export evidence with limitations for a bounded engineering decision.
Approved model and scenario choices, public software examples, current workbenches, Mission Control run inspection, evidence and provenance views, and a scoped evaluation walkthrough. Signed-in Mission Studio is available for configured persistent work.
A specific engineering question, the intended use and acceptance criteria, relevant inputs within supported configurations, and a technical reviewer to judge whether the disclosed model fidelity is adequate.
Public examples need no account or hardware. Mission Studio persistence needs sign-in and configured access. Arbitrary uploaded spacecraft models are not supported. Custom Mission Studio definitions do not automatically execute. Analysis is not certified or flight-qualified. Measured hardware correlation is not included.
A first evaluation is a bounded software run and evidence review using current curated capability. Every accepted subsystem model is currently unit-validated and reduced-order; no model is calibrated, flight-qualified or correlated with measured hardware. Model scope and limitations differ by subsystem. Generic customer composition and full lifecycle continuity remain future work.
Next: run a public example, request a demo, or discuss a scoped evaluation.
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 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
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.