cairn
Job · Satisfy the review

Screenshots of your admin console cannot leave with customer data in them.

The objection that stops a capture tool at the security review is not a feature gap — it is that the tool takes pictures of production. Cairn was built around that objection rather than around it.

Request accessEstimate your AI cost
In their words

Three sentences from security reviewers.

“Your tool screenshots our production admin. Explain the redaction.”

What Cairn does: Four tiers, with enforced policy redaction running at ingest — before any human sees the image. Strict originals mode encrypts the original, never serves it, and lets an admin delete it once a derivative exists.

“What stops the internal runbook appearing in a customer-facing answer?”

What Cairn does: Enforcement at retrieval rather than in the UI, plus cross-audience leak probes in CI on every build. A leak is a build failure, not an incident.

“Are you SOC 2?”

What Cairn does: No. We have not started a SOC 2 audit, and the security page will say so when we do. We would rather lose the deal than describe it as under way.

First thirty days

A pilot that a reviewer can actually approve.

Not a migration project. Each week produces something usable on its own, so you can stop at any point and still be ahead.

  1. Step 1Read the security page firstWritten for a reviewer, not a marketer. Tenancy, redaction, AI safety, egress, and an explicit list of what is still roadmap.
  2. Step 2Set policy before captureEnforced redaction rules and strict originals configured up front, so the first screenshot taken is already governed.
  3. Step 3SSO, SCIM, rolesSAML and SCIM provisioning, seven built-in roles from owner to viewer, and an exportable audit log wired before the pilot opens up.
  4. Step 4Pilot one internal audienceStart internal-only. Public publishing stays behind an approval policy until you are ready to turn it on.
What you actually use

Governance, redaction, and audit

The rest of the product is there when you need it. These are the parts this job leans on.

Security →The full control set: capture and redaction, tenancy enforced by the build, AI safety suites, deny-by-default egress, and the compliance split.
Capture →Masked at the source — field labels recorded, values never. An architectural rule with tests, not a toggle.
Knowledge →Per-audience governance with a content × audience matrix, custom audiences, and approval policy for public publishing.
AI agent →Grounding policy, regression-tested refusal, permissioned tool calls, and a fenced execution model for "do it for me".
Developers →Contract-first API, signed webhooks, an MCP server you run yourself (npm release coming soon), and the audience scopes enforced identically across all of them.

Where Cairn is the wrong choice

Three answers a procurement checklist will not like.

  • There is no SOC 2 report and no audit under way. If your policy requires one, we do not clear it today.
  • Patient-identifiable health information is prohibited; Cairn does not offer a HIPAA service or BAA. The DPA and processor register await verification and founder-approved publication. EU residency is unavailable.
  • There is no contractual uptime SLA yet. The published figures are internal service objectives and we will not dress them up as more than that.

Other jobs Cairn does

Ops & EnablementYour process lives in three people’s heads. One of them is leaving.Onboarding takes six weeks because the wiki was last true in March. Cairn captures the real process from the person doing it, and shows it to the next person inside the actual tool — not in a document about the tool.Support & CXYou answer the same forty questions forever. Cairn turns each answer into an asset.Your team already writes excellent documentation — one ticket at a time, then throws it away. Cairn keeps it, publishes it, grounds an agent in it, and tells you which question is still costing you the most.
Request accessAsk us about your caseInvite-only while we pilot