Ship what you said you'd ship.
Stint works in fourteen-day units. No infinite backlog. No roadmap fiction. A fixed window, and what actually got done.
The clock is the plan.
Every stint is exactly fourteen days. You pick what goes in on day one. You don't add work mid-stint. If something matters more, it goes in the next one. The window doesn't stretch.
Nothing auto-assigns.
Stint doesn't route tickets by last-seen or velocity. A human picks up the next thing. Teams that see their queue make better calls than teams whose tools pretend to.
The retro is already written.
When the stint closes, Stint writes the retro from what actually happened: completed versus carried over, who picked up what, where the time went. You edit. You don't draft.
We stopped lying to ourselves about what we'd get done. — Priya Venkatesh, engineering lead
Fixed cycles. Fixed prices.
No usage pricing. No per-seat surprise mid-quarter.
For solo work. One stint at a time, no archive limit.
- 1 active stint
- Unlimited archive
- Auto-generated retros
- One workspace
For teams that know the difference between a plan and a sprint.
- Everything in Personal
- Unlimited active stints
- Shared queue
- Cycle analytics
- Slack + GitHub integrations
For companies that need SSO, audit, and a DPA on the wall.
- Everything in Team
- SSO / SAML
- Audit logs
- DPA + custom deployment
- Dedicated CSM
Two weeks.
What do you actually want done by then?