Who runs it
The claim
It runs on your repositories, your issues, your board and your wiki, so the cost of removing us is zero.
That is not generosity. It is the only arrangement an enterprise should accept, because every other one prices your exit for later, when you will have less leverage than you have today. A platform that keeps the work somewhere of its own has quietly acquired a second product to sell you: the migration off it. This film is a procurement interview. The questions get answered against running screens, in the order a buyer actually asks them.
Reading the film
0:20 — two hundred and ten gaps, and phase one closing twenty one of twenty one. Then pull request twenty five, on the same card. The register itself is the Unboxing’s to prove; what this beat adds is that a gap has an owner, an answer, and somewhere the answer landed.
1:34 — what it is wired to, including what it is not. Five sources, three of them connected: a named GitHub repository, a named JIRA project, a Confluence space. Swagger and Figma read Not configured, in the same list and the same type as the ones that work. A connection inventory that lists only its successes is the one a security review cannot use.
1:50 — the queue as it is. Open seven. Closed zero. Closed in the last seven days, zero. Average age twenty days, six of them stale. Nothing rounded off and nothing closed to improve the picture. This is where the refusal earned in article five shows up somewhere it costs something.
2:50 — pull request forty seven, with the safety case written into it. Merged, six commits, forty two files changed, sixteen thousand and fifty lines added and twenty five removed. Under a heading that reads Safety / why this is low-risk it states what it does not touch and how it knows. The merge is still a person’s decision, in a reviewer’s tool, in your account.
3:09 — the chain, on one ticket. Auto-created by StellarView from support ticket QMGSUPPORT-2, linked back to it in the panel below, carrying its own estimate of five to seven developer days. Provenance is what lets an issue outlive its author.
4:02 — take it away in a year.
It runs on your repositories, your issues, your board, your wiki. The epics are issues on your board. The plans are commits in your repo. The documentation is pages in your wiki. Take StellarView away and every one of those stays exactly where it is, under your account, in your format. There is no export step because nothing was ever held somewhere else.
What stays that is not an artefact
The artefacts are the easy half of that answer. The harder half is what a team has after a year of working this way. Writing the safety case into the pull request, as at 2:50, is a habit before it is a feature. Linking an issue back to the ticket that caused it, as at 3:09, is a habit. So is publishing the queue at 1:50 without tidying it first. Those are patterns, and a pattern does not uninstall. The shared glossary a team builds while doing the work is theirs afterwards, and it is usually the most-read thing they own.
The price
Seventy two thousand a year, as a platform licence rather than per seat, because the value does not scale with how many people log in. It scales with how many systems it plans and builds. Start with a pilot at eighteen thousand, fixed, one document to a deployed build, credited in full against the first year.
What this costs, and what it does not do
This is a film of screens, so it shows where the artefacts live and not whether they are any good. The connection inventory at 1:34 belongs to one install and yours will be missing different things. The desk numbers at 1:50 are poor and they stay in, which is evidence of honesty rather than of a healthy queue. And the patterns above are the part with no plate on screen: nothing here shows a team a year in.
Six articles, and not one of them asked you to believe something you could not open. The last one costs a week.
The pilot →See it running
sue-ledger in the Stellarverse index →The same film, next to every other one, with the evidence for each sitting under the film that pays for it. No price and no form on that site.