Somebody texts you a screenshot. You retype it into a list. 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.
Request fulfilment, incident management, change enablement, release management — those four are not bureaucracy, they’re the reason work stops getting lost. The CAB, the approval chain, the service catalogue and the CMDB are what you add when you have an organisation to protect from itself.
So you get software built for a department, or nothing. And nothing means four disconnected tools plus your Saturday spent wiring them together.
I’ve run incident and change management professionally since 2007. This is that spine, at the size of one person.
A public page, a one-line embed per app, or a private link per client. No account for them, ever.
Ground Control ⟶Six people asking for one thing is one change with six names on it — and all six get told by the same landing.
Ground Control ⟶Drafted from what’s aboard the flight, in your voice, and published where they’ll actually read it.
Ground Control ⟶One setting renames everything to ITIL’s own words, for the practices whose reviewer expects them in writing.
Ground Control ⟶Most requests end at the reply. The ones that need a change carry the reporter’s words and screenshot with them, and the link home survives forever — in both directions.
No points, no sprints, no velocity, no burndown. You are the change advisory board.
“Isn’t this just a helpdesk with extra steps?”
A helpdesk is one of the five tools this replaces, and on its own it costs $15–55 a seat. Add an issue tracker, a feedback board, a changelog tool and something to quote with, and you’re at $96–325 a month for one person.
None of those five connect the request to the release. That seam is where the work goes missing, and closing it is the entire point.
No response-time targets, no breach warnings, no colour that means late. A ticket waiting twelve days might be waiting on someone else’s office.
Nothing closes because it got old. Old is not the same as done, and pretending otherwise is how trust goes.
Every customer-facing page is one link showing one thing. No logins, no password resets, no support load about support.
No. Plenty of people will buy this for the front door alone and never open a change record. Every step after the queue is optional.
Unknown senders confirm by email before the ticket appears, and any door switches off in one click without touching what came through it.
That’s the design. Each door tags which app it came from, and it all lands in one place.
You drop back to the standard queue with every ticket intact. Changes and flights go read-only and nothing is deleted.
That’s the whole first step, and it takes about a minute. If nobody but you ever files anything, switch it off — you keep the queue either way.
This is the short version of the site, cut down to what reads well on a small screen. The full thing — every instrument explained, the pricing configurator, the whole story — lives on the desktop site. So does the app: Cloudbase is meant to be worked from a real screen, at a desk, with your hands on it.