CubeSTEM

Programmes

Choose how your school runs MissionLab.

Four ways to start, from a first mission to a continuing school programme. Scope depends on your timetable, year groups and teacher support, so pricing is quoted per school rather than published.

Try a MissionRequest school pricing

School programmes

Start with one mission. Grow into a programme.

Mission Discovery

About 2 to 3 hours
Who it is for
A class meeting MissionLab for the first time
What students do
Run their first spacecraft mission from briefing to decision.
What the school receives
A guided first session and a clear view of what a mission looks like.
Book a first mission

Mission Sprint

About 6 to 10 hours
Who it is for
A class ready for a short engineering unit
What students do
Work through several guided missions and compare their results.
What the school receives
A bounded unit a teacher can plan, run and review.
Plan a Mission Sprint

Mission Season

Multi-week programme
Who it is for
A class or club running a full strand
What students do
Build a mission portfolio and prepare for the Challenge.
What the school receives
A repeatable multi-week programme with teacher guidance throughout.
Discuss Mission Season

MissionLab School

Continuing term or year programme
Who it is for
A school making space engineering part of its STEM offer
What students do
Progress across grade bands on the same spacecraft.
What the school receives
A continuing programme with progression, teacher support and review.
Request school pricing

Every rung runs in software on ordinary computers. Hardware is never required to complete a mission.

Other paths

Universities and optional hardware are scoped separately.

Universities and engineering programmes

University Digital Twin

A Digital Twin and Mission Control pathway for labs, coursework, capstones and verification-and-validation style engineering learning.

  • Course or lab objective mapping
  • Digital Twin workspace demonstration
  • Model, provenance and evidence review
  • A bounded Developer API and source clients for explicitly enabled local/private evaluation, not production-public access
Discuss university use

Add-on to any school programme

Optional hardware extension

A separately scoped kit or supervised KidSAT extension, discussed after the software programme, operator responsibility and commissioning status are understood.

  • Hardware suitability review
  • Operator and safety boundary
  • Training and local-console requirements
  • Physical acceptance and correlation gates
Ask about hardware

What a quote does not authorize

An education identity, subscription or quotation never activates physical hardware, operator control, official Challenge attempts or production deployment. Hardware acceptance, official competition and deployment remain separate human gates.

Request school pricingSee what a school getsContact CubeSTEM