Why we moved from Per-Seat to Usage-Based Pricing
For decades, the standard pricing model for B2B software has been "per seat". You hire a developer, you buy a Jira license, a GitHub license, a Slack license, and a Linear license. It makes sense for tools where human interaction is the primary metric.
The Problem with Seats
However, AI tools are different. GitSniff isn't a tool your developers "use" in the traditional sense. It's an agent that works alongside them. Some weeks, a developer might ship 10 PRs. Other weeks, they might be designing architecture or on vacation.
Charging a flat per-seat fee for a developer who didn't ship code that month feels wrong. It discourages adoption. We've seen teams restrict access to CI/CD tools to "save seats", creating silos where junior devs don't get the same tooling as seniors.
The Consumption Model
We believe in aligning price with value. Value in code review comes from insights generated. If Anitta finds a critical security bug, that's valuable. If she scans a massive refactor, that's valuable.
Our pricing model is simple:
- Input tokens (reading code) are cheap.
- Output tokens (generating reviews) cost slightly more.
- Zero monthly fees.
This allows you to install GitSniff across your entire organization without worrying about a ballooning bill during a hiring spree.
Enjoyed this article?
Subscribe to the GitSniff newsletter for more insights on engineering, AI, and code quality.