Everything we're building, in the order we're building it.
AeroVMS is pre-launch. There is no release history to publish and we are not going to invent one, so this page does that job instead: exactly what is being written now, and what comes after it. It is updated as the work moves.
Status legend
- Shipped
- In the product and usable. Not in a branch, not in review.
- Building
- Being written now. Everything below it is waiting on it, so it is the phase worth reading.
- Next
- Scoped and queued. It starts when the phase above it is finished, not alongside it.
- Later
- Committed in scope, not yet in detail. The items firm up as it gets closer.
Four phases, and they run in order.
Each one leans on the phase above it, so nothing further down starts early to look busy.
Nothing below is marked shipped yet. We would rather leave that state empty than describe work in the present tense before it is in your hands.
- P0Building
Foundations
The tenancy spine: a request hits your subdomain, resolves your airline, and queries your own database — provably, or it returns nothing.
- Per-airline database provisioning
- Subdomain routing and tenant resolution
- Fail-closed tenant assertion on every read
- Schema migrations across the whole tenant fleet
- Account, billing and subscription portal
- P1Next
First airlines flying
Everything an airline needs to hire pilots, publish a schedule, fly, and get scored PIREPs into logbooks.
- Crew centre: roster, profile, logbook, ranks, fleet and schedule
- Control dashboard: pilots, fleet, routes and the review queue
- ACARS ingest, validation and automatic scoring
- Checkout, tier entitlements and gating
- Full data export
- P2Later
Beta
Migration in, the live map, and the systems that make an airline feel like an airline.
- One-click phpVMS import
- Live map with realtime positions
- Virtual economy and hub finances
- Events, tours, awards and leaderboards
- Public API and webhooks
- P3Later
General availability
The things established airlines ask for before they will move a decade of history.
- Custom domains
- Enterprise SSO and white-label branding
- Published SLA and support tiers
- Hands-on migration for large rosters
Building it where you can watch.
A roadmap is only worth reading if the people writing it are willing to look bad on it. Four things we hold ourselves to.
- SAYWe say what is not built
- It costs nothing to write a page in the present tense, and it costs an airline a weekend to find out it was not true. Where something is not built, this page says so — including for the phases nobody has started.
- FNDFounding airlines move this list
- Early airlines get a direct line to the people writing the code, and what they ask for changes the order below.
- EXPBetting early stays reversible
- Full export of your database is on every tier, including the free one, at any time. If this roadmap goes somewhere you do not want to follow, you leave with the roster, the hours and every PIREP your pilots ever filed.
- LOGThis page is the changelog
- Until there is a release list worth keeping, this page is it. There is no separate changelog, no blog post standing in for one, and no version number doing the talking.
No dates, because we won't promise a month we can't hold.
A date on a page like this is a guess wearing a suit. Work written by a small team runs into things nobody scheduled, and the honest response is to take the extra week — not to ship something thin on the day a plan picked.
So the order is the promise instead. The phases above run top to bottom, each leaning on the one before it, and a phase changes state on this page the day it actually changes. Hold us to the sequence, not to a calendar.
Start the airline, and move this list.
Founding airlines are who this roadmap answers to. Set yours up on the free tier, tell us what you actually need, and watch it move up the page.
25 pilots free · No card · Export everything whenever you like