NewWrite and update your docs from Claude Code, Cursor or ChatGPT.
Start freeCairnbook drafts help articles from your release notes, refreshes screenshots when your interface changes, and sends every update to review before it goes live.
Audit · Aug 17 – Aug 24, 2026
Orrin can now edit existing images: pixelate sensitive regions, add arrows and resize. External images are copied so links keep working, and explicit screenshot requests are honored across multi-step guides.
Support and product teams at growing software companies publish with Cairnbook.
The problem
Product changes move quickly. Help content tends to move on its own schedule, and the gap between the two is where customers get stuck.
A redesigned settings page quietly breaks every guide that shows it. Nobody notices until a customer does.
Engineering ships the change, but the article that explains it waits in a backlog for weeks.
Without a clear record of each change, writers rebuild the new behavior from memory and pull requests.
Works with your tools
Cairnbook connects to the editors, repositories and chat tools your team uses every day, so updates start where the change happens.
Choose the repositories and release channels that describe your product. Cairnbook only reads what you select.
Link each article to the features it describes so changes route to the right page.
Review the proposed edits once. After that, routine changes arrive as small, reviewable updates.
Help center
Readers find the right page, and the page matches the product they are looking at today.
Getting started
12 articles
Billing and seats
8 articles
Integrations
21 articles
Troubleshooting
15 articles
Popular right now
Features
Every merged change becomes a draft article with the new steps, ready for an editor to approve.
Results rank by what people actually ask, with synonyms for the words your product uses.
Each edit arrives as a diff with the source change attached, so reviewers see what moved and why.
Publish the same articles to an in-app assistant that cites the page it used for each answer.
Links, anchors and embedded screenshots are tested on every publish and flagged before readers see them.
Set colors, type and layout once. Every article and screenshot follows the same rules.
Support
When an interface moves, the article that describes it is already in review. Customers stop reporting the same confusion.
Read the support storyProduct
Release notes become drafts the same day a feature merges, so the help center lands with the feature instead of weeks later.
See the release workflowWriters
Writers spend their hours on conceptual guides and edge cases, while routine screenshot and wording updates happen in review.
Meet the writers toolkitMigration
Bring your existing articles, folders and images across. The import keeps links working and flags anything that needs a human look before it goes live.
Import progress
2 of 3 steps
Connect your current help site
Done
Map folders to categories
Done
Review the first drafts together
In progress
We used to learn that an article was wrong from a support ticket. Now the update is waiting in review the same day the feature ships.
Priya Raman
Head of Support, Lanthorn
The screenshot refresh alone paid for the first quarter. Our writers stopped redrawing the same three menus every sprint.
Tomas Lindqvist
Documentation lead, Foxglove Analytics
Migration was boring in the best way. The import matched our folders and the first drafts were close to right.
Amara Okafor
Product manager, Brightline
FAQ
Still unsure about something? Send us a note and a person on our team will reply within one business day.
Cairnbook reads the merged pull requests and release notes connected to your product. When a change touches something a published article describes, it opens a draft update for an editor.
No. The first draft of most articles is generated from release notes and your existing pages. Editors refine the wording and approve each change before it is published.
Yes. Every automatic update is a proposed change with a visible diff. Nothing is published until someone on your team approves it, and you can require two reviewers for chosen sections.
Cairnbook captures screenshots from a staging copy of your product and replaces outdated ones when the interface changes. You can pin any screenshot to stop automatic replacement.
Yes. The migration tool reads articles from the most common help platforms and maps your folders to categories. You review the first drafts before anything goes live.
Article content and screenshots are stored in the region you choose during setup. Your articles are never used to train models, and you can export everything at any time.