GitPrime Is Gone: What Happened to Pluralsight Flow and What to Use Instead

If you're looking for GitPrime, you're looking for something that no longer exists under that name. GitPrime was acquired by Pluralsight in 2019, rebranded as Pluralsight Flow, and then folded into Vista Equity's private-equity roll-up of Pluralsight in 2021. Here's the full story — and where engineering teams are going now.

The GitPrime Story

GitPrime was founded in 2015 by Travis Kimmel and Davida Rivka in Durango, Colorado. At the time, engineering managers had almost no visibility into how their teams worked. Velocity was measured in story points (a deeply imperfect proxy), and questions like "which teams are shipping fastest?" or "where is review time piling up?" required manual analysis of GitHub data that nobody had time to do.

GitPrime changed that. It connected to GitHub and surfaced PR cycle time, review participation, coding days, and throughput in a clean dashboard. It was arguably the first product that made engineering metrics accessible to non-engineers — engineering managers could finally open a dashboard and understand what their team had shipped last week without asking a developer to write a query.

The product grew quickly among engineering-led companies in 2016–2018, particularly in the software-as-a-service sector. It pioneered what is now called the "engineering intelligence" category.

The Pluralsight Acquisition (2019)

In March 2019, Pluralsight acquired GitPrime for an undisclosed sum. Pluralsight, then a publicly traded developer skills platform, saw GitPrime as a natural extension of its mission: if you're already tracking developer skills development, why not also track developer output?

Pluralsight rebranded GitPrime as Pluralsight Flow and integrated it into its product suite. For the first year or two post-acquisition, Flow continued to receive product investment — the team shipped DORA metric dashboards (deploying the research from the DORA State of DevOps reports), improved team benchmarking, and added more Jira integration capabilities.

The original GitPrime founding team eventually departed, as often happens post-acquisition. Without the original product vision driving it, Flow began drifting toward maintenance mode.

The Vista Equity Takeover (2021)

In December 2020, Vista Equity Partners announced it would take Pluralsight private for approximately $3.5 billion. The deal closed in early 2021. Vista Equity is a private-equity firm that specializes in enterprise software acquisitions, and its standard playbook is well-documented: cut costs, focus on revenue retention, reduce R&D investment, and optimize for EBITDA.

For Pluralsight Flow, this meant the product entered a slow freeze. Feature development slowed significantly. The engineering team was reduced. The integration roadmap that Flow users had been expecting — better incident management integration, AI-powered analysis, risk prediction, coverage tracking — never materialized.

Meanwhile, competitors were shipping rapidly. Swarmia added Linear integration and developer experience metrics. LinearB shipped an automation layer for PR workflows. Jellyfish expanded its business alignment reporting. And newer entrants like Koalr built deployment risk prediction, AI chat, and CODEOWNERS enforcement from scratch as first-class features — things Flow never added.

What Pluralsight Flow Looks Like Today (2026)

Pluralsight Flow still exists as a product. It still has customers. The core DORA dashboard functionality, PR analytics, and GitHub/Jira integration still work. If your team signed up for Flow four years ago and the basics are sufficient for your needs, you're probably still getting value from it.

But the product is frozen relative to the market. Pricing remains enterprise-only (contact sales), which prices out teams that were considering it. The roadmap shows little in the way of AI, risk prediction, or new integration work. Support response times have stretched. Teams that need more than the 2020-era feature set are leaving.

Where Engineering Teams Are Going

Teams leaving GitPrime / Pluralsight Flow in 2026 are generally moving to one of four platforms, depending on their priorities:

The GitPrime Legacy: What It Got Right

Whatever has happened to the product since the acquisition, GitPrime deserves credit for what it established. It proved that engineering managers want data about how their teams work — not just story point velocity, but actual code metrics. It demonstrated that PR cycle time is a meaningful signal. It popularized DORA metrics (alongside the DORA research) among engineering leaders who had never heard of deployment frequency or change failure rate.

Every tool in this category stands on the foundation GitPrime built. The question for engineering teams today is what comes next: the baseline capabilities GitPrime established are now table stakes, and the differentiation is in what you build on top of them.

Deployment risk prediction. AI-powered analysis. CODEOWNERS governance. Coverage integration. The engineering intelligence category has moved far beyond where GitPrime left it.