Everything is two keys away
⌘K moves, assigns, labels and files any issue from anywhere in Cairn, without reaching for the mouse.
Cairn keeps issues, sprints and roadmaps in one calm workspace, and writes the updates for you. Your team spends the week building, not reporting.
Free for teams up to 10 · Import from Jira in minutes
Split the checkout service from orders
Address autocomplete for 14 countries
Promo codes: stack rules and limits
Card payments time out on 3-D Secure
Retry failed payments with backoff
Saved cards list on the account page
Apple Pay sheet for the mobile checkout
Order summary empty and error states
Receipt emails in the customer's language
Checkout v2 visual QA on Safari
4,000+ product teams plan their next release in Cairn.
The workspace
The board in the hero is one lens. Switch to the inbox, the sprint or the roadmap, and every number comes from the same issues.
The current sprint, its burndown, and what Autopilot will roll over.
Async by default
Every morning Cairn reads the board and posts what shipped, what moved and what's stuck. Nobody types it, and nobody has to sit through it.
Meetings on the team’s calendar
7h 45ma week
Features
Nothing here is a module you switch on. It is all part of the same workspace, from the first keystroke to the release note.
⌘K moves, assigns, labels and files any issue from anywhere in Cairn, without reaching for the mouse.
Build automations from plain sentences. When this happens, if that's true, do these things. No scripts to maintain.
Autopilot carries unfinished work into the next sprint at midnight, history and estimates intact.
See how long work really takes to ship, by team and by label, and whether it's getting faster.
120+ integrations with two-way sync. Commits, errors, designs and calls all link back to the issue they belong to.
How it works
Follow one bug through Cairn. Nobody copies a link, updates a status or writes a release note by hand.
Sentry, Slack, a support email or a teammate. Everything lands in one inbox.
It suggests an owner, a priority and a sprint. One key accepts all three.
Name the branch after the issue, and status follows the code from review to merge.
The issue closes, the release note writes itself, and the channel hears about it.
Customers
“We moved 40,000 issues over a weekend. On Monday nobody asked where anything was, which is the best review a tool can get.”
“The first tracker our designers open without being asked.”
“Sprint planning used to eat Tuesday afternoon. Now it's twenty minutes, because the board already knows what rolled over.”
Security
Pricing
Every plan has unlimited issues, boards and history. Upgrade when you need sprints at scale or a security review.
For small teams finding their rhythm.
$0per person
per month
For product teams running sprints every week.
$8per person
per month, billed yearly
For companies with a security review.
$14per person
per month, billed yearly
More than 500 people, or need your data in a single region? Talk to us about Enterprise
FAQ
Still deciding?
Our team answers in under an hour on weekdays, and we’ll run your Jira import with you.
Chat with usYes. The importer brings issues, comments, attachments, sprints and custom fields, and keeps the old keys as aliases so links in pull requests still resolve. Most teams finish in under fifteen minutes.
The board is one view of the work. Cairn also runs your sprints, rolls unfinished issues forward, links every issue to the pull requests that close it, and shows the roadmap that all of it adds up to.
No. Rules are built from a trigger, an optional condition and one or more actions, in plain sentences. Teams who want more can call the same actions from the API or a webhook.
Anyone who can create or be assigned issues. Guests who only view and comment are free on every plan, so stakeholders never need a seat.
In the EU or the US, your choice, encrypted at rest and in transit. Business plans add data residency, an audit log and SSO.
You keep everything. If you don't upgrade, the workspace drops to the Free plan, and nothing is deleted.
No card needed. Bring your Jira issues with you.