Appfire Flow migration
Your Flow renewal was refused. Here is the self-hosted option.
Appfire Flow — Pluralsight Flow before that, and GitPrime before that — stopped accepting renewals on 30 June 2026 and runs in maintenance until its end of life on 31 December 2027. Every alternative Appfire itself recommends is operated by its vendor. Deckgauge is the one you run yourself.
SELF-HOSTED · FREE AND UNCAPPED CORE · NOTHING LEAVES YOUR NETWORK
The dates, so you can work out how long you actually have.
- 30 June 2026 — renewals ended. Flow can no longer be renewed at any price.
- A 60-day grace period was granted where a renewal fell in July or August 2026, explicitly so those customers could assess alternatives. The last of those cohorts is out around the end of October 2026.
- 31 December 2027 — end of life. Maintenance and security work until then; no new capability.
If you are inside the grace period, the deadline that matters is the end of it, not the 2027 date. The 2027 date is when the lights go out; the grace period is when the decision gets made for you if you do not make it.
Appfire's own list is five products that someone else operates.
The alternatives Appfire recommends — LinearB, Jellyfish, DX, Allstacks and Swarmia — are all good products, and every one of them is run by its vendor. None is something you install on your own hardware and operate yourself. That is the axis this page is about, and it is the one nobody on that list is going to raise with you.
Be precise about what you are asking for, though, because the vendors have got better at this. If what you need is "our data stays in our region", DX now sells a single-tenant deployment with data residency, and another that runs inside an AWS or GCP account you own — DX still operates both, and both are enterprise-gated and quote-only, which is its own answer at a mid-market size. What is still true only of a product you host is the whole sentence: nothing leaves, no vendor operates it, you can read the source, and it starts at $600 / month. If your reason for Flow was an on-premises Git server, a works council, or an unwillingness to have anyone else hold the data at all, that is the difference that matters.
There is a second shape to the list worth knowing before you book five demos. Three of the five are Gartner Magic Quadrant Leaders. Two of them — Atlassian (DX) and Jellyfish — publish no price at all, so the first number you see arrives after a call. The other, LinearB, publishes a per-developer rate but will not sell below 50 developers, which is its own answer if your engineering organisation is smaller than that. Our number is on the pricing page, starting at $600 / month from the first engineer, and the self-hosted core is free at any size.
There is nothing to export.
This is the part that surprises people. Flow did not hold original data — it derived its analytics from your Git provider and your tracker. So does Deckgauge. It connects directly to GitHub, GitLab, Azure DevOps and Jira and rebuilds the history from the systems of record, which still have it.
That means no CSV extract from a product you are losing access to and no warehouse migration. It also means you can stand Deckgauge up beside Flow for the rest of your grace period and compare the two on the same weeks of real data before you commit to anything.
How far back it reaches depends on the source, and it is worth knowing before you assume the series is continuous. A GitHub source backfills twelve months by default. An Azure DevOps source is forward-only out of the box — its history backfill is opt-in, because it multiplies request volume against an API that throttles — so if you need the old quarters on an ADO estate, turn it on deliberately at install time rather than discovering the gap in your first board review.
What you get back on the other side: DORA metrics and delivery flow, review analytics, cycle time and throughput, investment allocation, CapEx/OpEx timesheet reporting, an org chart with per-engineer workload, and a Monday-style board and roadmap over the same sources — all of it on your own hardware.
Four things, before you find them yourself.
- Five connectors, not a catalogue: Jira, GitHub, GitLab, Azure DevOps and a calendar source, plus Microsoft Graph for org structure. If your estate runs on something else, we are not the answer yet.
- No developer-experience survey. Everything here is derived from systems data. If you want sentiment measured, pair us with a survey tool — we do not have one and are not going to pretend otherwise.
- No SOC 2 report and no Magic Quadrant placement. What we offer a security review instead is the source code, which you can read.
- You operate it. A Postgres, a ClickHouse, a Redis and a Keycloak, backed up and upgraded by you — unless you would rather we hosted it, which is what the paid plan is.
What people ask when their renewal has just been refused.
Is Appfire Flow being discontinued?
Yes. Appfire Flow — previously Pluralsight Flow, and GitPrime before that — stopped accepting renewals on 30 June 2026 and is in maintenance mode until its end of life on 31 December 2027. Customers whose renewal fell in July or August 2026 were given a 60-day grace period to assess alternatives, which puts the last of those cohorts out around the end of October 2026.
What is the self-hosted alternative to Appfire Flow?
Deckgauge. Every vendor on Appfire’s recommendation list operates the product for you — none of them is something you install and run yourself. Some now offer a single-tenant deployment with data residency, or one that runs inside a cloud account you own, but the vendor still operates it and both are enterprise-gated and quote-only. Deckgauge runs entirely on your own infrastructure — Postgres, ClickHouse, Redis and Keycloak in your network, with the LLM inference for its advisor on the same box — and the self-hosted core is free and uncapped.
Do I have to export my data out of Flow before it shuts down?
Not for Deckgauge. Flow derived its analytics from your Git provider and your tracker, and so does Deckgauge — it connects directly to GitHub, GitLab, Azure DevOps and Jira and rebuilds the history from the systems of record. There is no Flow export to migrate, and nothing is stranded in a warehouse you are about to lose access to.
What does Deckgauge not do that Flow did?
Flow shipped a large connector catalogue and a support organisation behind it. Deckgauge connects to five sources (Jira, GitHub, GitLab, Azure DevOps and a calendar) plus Microsoft Graph for org structure, has no developer-experience survey instrument, and has no SOC 2 report. If any of those is a requirement, it is a requirement we do not meet today and it is better to know now.
How much does it cost?
The self-hosted core is free, uncapped and licensed under the FSL-1.1-Apache-2.0, which converts to Apache-2.0 two years after each release. If you would rather we hosted it, or you want a commercial licence, the price is published on the pricing page rather than quoted after a sales call.
Try it on the live demo before you install anything, read the licence if that is the question, or write to support@codpal.com and a person will answer.