Real ArduPilot · Linux · Fully offline
SITL Drone GCS runs a real ArduPilot flight stack in simulation on ordinary Linux machines. No compiler, no build step, no dependency hunt. Students fly, and the telemetry the autopilot actually produced decides the grade.
The core bet
A student’s score is computed from the flight telemetry the autopilot actually produced, checked by anti-cheese rules and airborne-liveness gates. You cannot pass by writing plausible code. The drone has to do the thing.
Objectives are measured against what the flight stack reported in the air, not against the shape of a student’s program.
Solutions that satisfy an objective by accident, or by exploiting it, are detected rather than rewarded.
A mission that never leaves the ground scores nothing, however correct the code that failed to fly it looks.
Everything else is built on that one property. Badges, certificates, transcripts, class analytics and the credential chain all trace back to a grade that was earned in the air.
Capabilities
A flight simulator on its own does not run a classroom. Each pillar below is a distinct set of people with a distinct problem.
A real flight stack, driven properly.
A path from blocks to code to graded flight.
The half of the product teachers live in.
Evidence a student, a parent or an employer can hold.
Built for the person who runs the lab on Monday.
Why it holds up
Every vendor says offline and bilingual. These are the specific mechanisms behind ours, so you can check them rather than take them.
No cloud, no accounts, no student data leaving the building. That is enforced rather than promised: a declared registry lists every network-capable part of the system, and a guard test fails the build if anything gains network capability without an entry.
For a procurement officer, “grades are personal data and never leave this machine” is a claim that survives an audit.
Grade cards become plain-language coaching: an encouraging verdict, a per-objective why-and-fix, whole-flight habit notes, and one drill to practise next. Entirely offline and rule-based. It explains the grader; it never re-grades.
A paid model path exists as a dormant bring-your-own-key option, off until a user pastes their own key.
Enforced English and Arabic key parity, a lint gate that fails on any bare string literal in the interface, and a right-to-left mirror pass over the widget tree. The content is translated too: mission briefings, objectives, hints and tutorial steps.
Translation files provably cannot alter grading, so a student’s score is identical in either language.
See it working
Three views a teacher spends most of their time in. Everything here is the running application.
The frames below are schematic illustrations, not product captures. Replace with real screenshots before launch.
Survey, corridor and structure patterns over real terrain, with the geofence drawn rather than assumed.
Every score traces back to the telemetry that produced it, broken down by the skill it measures.
Plain-language coaching generated offline from the grade card. It explains the grader, it never re-grades.
Credentials
Grading is only worth as much as the record it produces. Credentials are cryptographically signed, so a third party can verify one without contacting the school, without a database, and without an internet connection.
Each credential carries a detached Ed25519 signature over its canonical payload. Change any field, whether a name, a score or a date, and verification fails.
A root key endorses a school’s key once. The school then signs its own students’ credentials locally. A verifier embeds one key and never needs updating when a new school is added.
The student holds their own credential. There is no server to query, no registry to maintain, and no personally identifiable information stored anywhere outside the school.
The credential states that a student completed simulated flight missions graded automatically from telemetry. It is a training record, not a licence to operate an aircraft, and that wording is carried inside the signed payload so it cannot be reworded afterwards.
Credential
Signature
Ed25519 · verified offline
In development. The signing core is built and tested. Certificate issuance and the public verification page are in progress.
Editions
Entitlements are checked locally against a signed licence file. No account, no activation server, no seat phoning home mid-lesson.
Placeholder packaging. Tier names, contents and pricing are not final and must be replaced before launch.
A single teacher, one room, one machine at a time.
A teaching team sharing rosters and results.
A whole school, with the lab operations tooling.
Multi-site, with programme-level reporting.
Get it
Install and fly. No compiler, no build step, no dependency hunt, no account to create, and nothing to configure before the first flight.
Supported platforms are being confirmed. Check with us before planning a rollout.
Single packageInstaller URL pending
Requirements
Questions we actually get
No. Flying, grading, coaching, mapping and credential verification all work with the network off. Updates can be delivered from a USB stick, and classroom sync runs over the local network or USB. Air-gapped labs were designed for, not accommodated afterwards.
Nowhere. There is no cloud service, no database and no runtime account. Grades and flight logs stay on the machine that produced them. A privacy console performs real erasure, and a declared registry plus a build-failing guard test is what stops a future change from quietly altering that.
No. The product runs a real ArduPilot flight stack in software-in-the-loop simulation on ordinary lab machines. That is the point: students fly a genuine autopilot without a budget for airframes, a flying area, or the risk that comes with both.
Grading reads the telemetry the autopilot produced, checked by anti-cheese rules and airborne-liveness gates. Code that looks right but never flies scores nothing. That property is the reason the rest of the product, from badges to credentials, is worth anything.
Real. English and Arabic key sets are identical and parity is enforced by a build gate, a lint gate fails any bare string literal in the interface, and the layout is mirrored for right-to-left. Mission briefings, objectives, hints and tutorial steps are translated, not just the menus.
That a student completed simulated flight missions graded automatically from telemetry. It is a training record, not a licence to operate an aircraft. That wording is carried inside the signed payload so it cannot be reworded on a certificate afterwards.