A proper front door for the people you build things for. They file a request, you work it, and if it costs money you quote it — then the change ships and everyone who asked gets told, without you writing a single email.
Somebody texts you a screenshot. You retype it into your task list. You quote the work in an email you'll never find again. The fix happens in your editor, the release happens in your terminal — and the person who asked finds out three weeks later, by asking again.
Nothing in that chain is hard. All of it is seams, and every seam is a place where somebody's request quietly dies. The big tools solve one seam each and cost more than your hosting.
Ground Control's only real job: nothing is re-typed, and nobody has to chase you.
A public page, a one-line embed in any app's help section, or a private link per client. Two fields and a screenshot. No account for them, ever.
Three lines, a number, and what's not included. They accept, counter or decline on the link they already have.
One button, carrying their words and screenshot. Six people asking for one thing is one change with six names on it.
Release notes drafted from what's aboard, in your voice. Pre-flight asks and never blocks.
On their own request, in their own words, on the day it lands. That last mile is the whole product.
Nobody sells this as one thing at this size. So you buy a helpdesk, an issue tracker, a public roadmap, a release-notes tool and something to quote with — then wire them together with your own hands and re-type between them anyway.
The three-seat column assumes two of you work tickets: base $24 + two seats at $9 + Ground Control for two at $12 = $66, and video is a separate Instrument that isn't in this table.
List prices, Aug 2026Built by someone who has run incident and change management professionally since 2007 — and still does, every day. This is that discipline with the parts that genuinely prevent lost work, and none of the parts that exist because a large organization needed a paper trail for its own sake.
You are the change advisory board. I've sat in those meetings since 2007 — a CAB, an approval chain and a service catalogue all exist to protect a large organization from itself, and you are not a large organization.
One setting renames everything — service request, incident, change record, release, known error — for the practices whose auditor expects them in writing.
Hangar › Taxiway › In the air. Three, because you have three — a fourth would be a lie about how you work.
No response targets, no breach warnings, no colour that means late. A request waiting twelve days might be waiting on someone else's office.
One app or nine. They find bugs, they want things, and right now that arrives as email you'll lose.
Client sites, an internal tool, somebody's WordPress. The requests are real work and nobody's tracking them but you.
Someone wants to see that changes were recorded, tested and released deliberately. One switch renames everything to ITIL's words.
No, and they never will. A link is the access. They see their own request and nothing else — not your notes, not the change record, not anyone else who asked.
Unknown senders confirm by email before the ticket appears. Any door switches off in one click without touching what came through it.
No. Plenty of people buy this for the front door alone and never open a change record. Every step after the queue is optional.
A helpdesk is one of the five tools this replaces — and none of the five connect the request to the release. That seam is where the work goes missing, and closing it is the entire point.
Not today. It's an instrument, not an app — it bolts onto the ticket queue you already have and borrows your clients, your projects and your time tracking. That's the point of it.
You drop back to the standard queue with every ticket intact. Changes and flights go read-only, the intake links stop accepting, and nothing is deleted.
That's the whole first step, and it takes about a minute. If it turns out nobody but you ever files anything, switch it off — you keep the queue either way.