Speed is a feature
A board that takes three seconds to load gets checked less often, and a tracker nobody checks is worse than no tracker. We budget every interaction rather than adding a spinner and moving on.
About us
We build the tracker we wanted to use
Sprint Guage started as an internal tool for our own delivery teams. It got good enough that keeping it to ourselves stopped making sense.
- Product modules
- 9
- Free users included
- 10
- Per user, billed annually
- $6
- Credit cards to start
- 0
What we believe
Four principles, applied ruthlessly
Every product decision gets checked against these. When they conflict, speed and data ownership win.
Depth without the tax
Powerful does not have to mean an eight-week rollout. Sensible defaults get you running in ten minutes, and the settings you do get are ones you will actually change.
Your data is yours
Full export in four formats, on every plan, at any time. No hostage-taking on downgrade and no deletion when a trial lapses. Leaving should be as easy as arriving.
Ship, then polish
Modules built one at a time, each finished before the next began. We would rather ship nine things that work than advertise fifteen that nearly do.
How we got here
The short version
The problem
Trackers that get in the way
We ran delivery teams on legacy tools for years. The pattern never changed: weeks of scheme configuration, a query language to learn, and a board slow enough that people kept a spreadsheet on the side.
The decision
Rebuild it properly
We picked the parts teams touch every day — boards, backlog, sprints, time, reporting — and rebuilt those properly, rather than reproducing a configuration layer most teams never open.
The build
One module at a time
Auth and organisations, then projects, issues, boards, sprints, roadmaps, time tracking, search, analytics, notifications, AI, admin, export, docs, and mobile polish.
Today
In production, and open for teams
The platform runs a real engineering organisation every day. It is now available to teams outside our own, on the same infrastructure and the same release cadence.
Built on boring, proven infrastructure
Nothing exotic. PostgreSQL for durability, Redis for queues and caching, a dedicated search engine for instant lookups, and WebSockets for the real-time layer. The interesting engineering is in the product, not the plumbing.
- TypeScript
- Next.js
- NestJS
- PostgreSQL
- Prisma
- Redis
- Typesense
- WebSockets
- Tailwind CSS
Move your team over this week
Create a project, pick your statuses, and have your first sprint running the same afternoon. Free for up to 10 users.
No credit card required · Cancel any time · Export your data whenever you like