Triage inbox
Every incoming bug and unassigned issue lands in one queue with a keyboard-only path through it. Most teams clear it in a minute a day.
New Cycles now roll over on their own
Your roadmap shouldn't need a meeting.
Kindle Holdings runs your team on two-week cycles that close and reopen without anyone dragging a card. Issues and bugs take their status from your pull requests. The roadmap redraws itself while you're still in standup.
Free for up to 10 people. No card, no sales call.
Cycle 14
Mar 3 – Mar 14
Progress
0%
Engineering teams shipping every two weeks on Kindle Holdings
- Northwind
- Parsec Labs
- Heliograph
- Tidewater
- Atlas Freight
- Verge Studio
The cycle
Two weeks. Then it happens again.
Every other tracker asks you to invent a process. Kindle Holdings ships with one, and it only has four moments. This is the entire method — there is no workflow builder, because there is nothing left to build.
-
Mon · week 1
Cycle opens
Kindle Holdings pulls the top of your backlog to fill the team's usual throughput. Argue with the list, don't build it.
-
Wed · week 1
Scope locks
New work still gets filed — it just lands in the next cycle. The commitment stops moving so the estimate means something.
-
Thu · week 2
Ship
Merged pull requests close their issues. Nobody updates a board on Friday afternoon to make the report look right.
-
Fri · week 2
Rollover
Unfinished work moves forward with its history intact, and the next cycle opens already loaded. Nothing is archived without you.
Status
Status should be a side effect of the work.
Connect GitHub or GitLab once. Branch names carry the issue ID, and every event after that moves the issue on its own. The board is accurate because nobody maintains it.
- Branch, PR and merge events map to status both ways
- Reverts reopen the issue with the revert linked
- Deploy webhooks mark what actually reached production
github → kindle
- push cad-412-debounce-rollover In Progress
- pull_request opened #1841 In Review
- pull_request merged into main Done
- revert 4c1e9ab on main Reopened
- deployment production · v2.41.0 Shipped
Speed
Nothing worth doing is more than one keystroke away.
Kindle Holdings is built for people who file twenty issues a day. Every action has a key, the command bar reaches all of them, and the whole app runs on a local cache so it answers before the network does.
- Offline by default — writes sync when you reconnect
- Bulk-edit a filtered view without leaving the keyboard
- Rebind anything, or import your Vim muscle memory
shortcuts
C
New issue⌘K
Command barGC
Go to current cycleA
Assign to someoneS
Change status⌘⇧P
Move to next cycle/
Filter this view⌘Z
Undo, including bulk edits
Roadmap
A roadmap that tells the truth without being asked.
Projects are made of issues, and issues live in cycles — so the roadmap is a calculation, not a slide. When a cycle slips, the bars move that afternoon and everyone who follows the project hears about it once.
- Forecasts built from your real throughput, not guesses
- One update per project per week, written for people outside the team
- A public read-only view you can hand a customer
roadmap · q1
C13C14C15C16
Webhook v2
On track
Cycle rollover
Shipping
SAML & SCIM
Planned
Mobile triage
Planned
Also included
The parts you'd otherwise buy separately.
Sub-issues
Split a large thing into small things and keep the parent's progress honest. Nesting stops at two levels, on purpose.
Cycle history
Every past cycle is preserved with what was committed, what shipped, and what moved — so throughput is measured, not remembered.
Slack digests
One message when a cycle closes, not one per status change. Threads reply back into the issue.
Saved views
Any filter becomes a view your whole team can open, subscribe to, or pin to the sidebar.
API & webhooks
GraphQL and REST with the same shape as the app, plus signed webhooks and a CLI. Rate limits published, not guessed.
From teams that switched
Fewer rules. Same work, out the door.
We deleted forty-one automation rules the week we moved over. Nobody has asked for one back.
Standup went from twenty-five minutes to six, because the board was already right when we opened it.
The rollover is the whole product. Our carryover went from forty percent of a cycle to twelve in a quarter.
Pricing
Priced per person, not per feature.
Everything about how work is tracked is in every plan. You pay more only when you need the things a security review asks for.
Free
$0forever
For a small team that wants a tracker to disappear into the background.
Create a workspace- Up to 10 members, 2 teams
- Unlimited issues and sub-issues
- Triage inbox and saved views
- 90 days of activity history
Most teams
Standard
$10per member / month
The full method: cycles, rollover, roadmap and git sync, for the whole company.
Start 14-day trial- Everything in Free, unlimited teams
- Cycles with automatic rollover
- Roadmap, projects and public views
- GitHub, GitLab and Slack sync
- Unlimited history and cycle analytics
Business
$18per member / month
For companies whose procurement team has a spreadsheet of questions.
Talk to us- Everything in Standard
- SAML SSO and SCIM provisioning
- Audit log and data residency (US or EU)
- Custom fields and issue templates
- Four-hour first response, business hours
Questions
The things people ask before switching.
01 How is this different from Jira?
Kindle Holdings has one opinion: work happens in fixed two-week cycles. There is no workflow builder, no field schema, no board configuration — and therefore no quarterly meeting about any of them. You give up flexibility you probably never wanted, and get a tracker your team doesn't have to be trained on.
02 Can we bring our history with us?
Yes. Direct importers for Jira, Asana, GitHub Issues and Linear, plus CSV. Comments, attachments, sub-issue links and assignees come across; closed issues keep their original close date so your throughput history stays real.
03 What happens to work we don't finish?
At cycle close, anything not done moves to the next cycle with its full history and keeps its position in priority order. It is never archived, hidden or silently dropped — and the cycle report records exactly what moved, so carryover is a number you can watch.
04 Do you offer self-hosting?
Not today, and we would rather say so than sell you a roadmap item. Business plans choose US or EU data residency, get a daily encrypted export you own, and a SOC 2 Type II report on request.
05 What if two weeks is wrong for us?
Cycle length is configurable from one to four weeks per team, and teams in the same workspace can differ. What isn't configurable is having cycles at all — that's the part the rest of the product is built on.
Cycle 15 opens Monday
Put your team on a two-week rhythm.
Import from your current tracker, pick a cycle length, and run one cycle. If it isn't better by the rollover, take your data and go.
Free for up to 10 people · Import in under an hour · Export anytime