Your documentation says one thing. Your team does another.

Cairn maps how your business, its teams, and individual contributors actually work day to day. It asks employees short questions in Slack, email, or the web, turns their answers into structured facts with provenance and a freshness score, and gives you a queryable account of how work really gets done — including the workarounds that never make it into documentation.

No, and it is not trying to be. Documentation captures how-to knowledge: what someone should do. Cairn captures how-does knowledge: what actually happens, who really owns it, which tool is genuinely being used, and as of when. Nobody is asked to write or maintain a page.

No. Keep them. Cairn is designed to sit alongside the knowledgebase you already pay for, not to become a second one — and it does not touch it. Cairn has no integrations into your documentation and does not read it.

Through your own AI agent, not through an integration we build. Cairn runs an MCP server. Most documentation tools now offer one too, so you point the agent you already use at both and ask it where they disagree. A typical finding: a runbook names a tool you pay for, but several people told Cairn they stopped using it because it is too slow and now work in a shared document instead. The agent surfaces the contradiction; Cairn supplies the half nobody wrote down, with names and dates attached.

The design target is a minute or two at a time. Questions arrive one or two at a time on a cadence that ramps down as coverage improves, and respect quiet hours, snoozes, and a cap on how often any one person is asked. People answer in their own words, in the tool they already have open.

Slack and email, with a web conversation page reached by a link in the prompt. Answers can be typed or spoken, and voice is transcribed for review before it is submitted.

Yes, and this is deliberate. Cairn proposes its reading of what someone said and that person confirms or corrects it before anything is recorded. Every contributor has a page showing everything attributed to them, which they can amend at any time.

That depends entirely on what they believe happens next, which is why Cairn records how work is done rather than how hard anyone works. There are no productivity scores and no per-person output metrics, contributors control their own statements, and process concerns route to admins as process problems rather than as individual performance.

That is a core use case. Cairn exposes a permission-aware REST API and an MCP server with personal and organization tokens. Answers come back with provenance, freshness, and confidence attached, and respect the same visibility rules a person in that role would get.

Knowledge is open within the organization by default, and admins can restrict visibility by group, team, or role. Permissions apply identically to people and to API and MCP queries, so an agent cannot read something its token holder could not.

Not yet. Our SOC 2 and GDPR programs are in progress and we will say so plainly until they are complete. Today Cairn encrypts data in transit and at rest, encrypts integration tokens at the application layer, supports GDPR data export and erasure, and keeps a customer-facing audit log.

Cairn is pre-launch and onboarding teams in cohorts. Pricing is not published while we are onboarding our first cohorts, because we are still learning which shapes of team get the most value. Joining the waitlist puts you in line for an onboarding slot, and waitlist members get pricing and early-cohort terms before anyone else.