FOR SAMD TEAMS

A regulatory expert in every tool you already use.

Cairn reviews your code, docs, and tickets as you work — flagging issues the moment they appear and helping you get through filing painlessly.

GitHub example-device · PR #12
Open Regulated-path update 2 files changed
demo-engineer @Cairn review this for IEC 62304 / FDA design-control impact before merge.
Cairn compliance review @cairn review
HIGH severity

Document impact assessment is missing

This PR changes a regulated code path but updates no tests, risk file, or validation evidence. Add the missing record — or note why none is required — before merge.

example rubric · pr_review.documentation_required
Google Docs Intended Use & Indications
D
Intended Use & Indications Editing - Draft
Cairn

This intended-use claim needs a supporting clinical reference before it can be submitted.

example citation · FDA guidance §IV
Jira DEMO board
DEMO board Compliance review
DEMO-14 Add alert-threshold risk control no trace
DEMO-19 Verification protocol stale
DEMO-21 Update intended-use text linked
Activity

This requirement has no verification evidence linked to it yet.

Cairn - example citation · requirement REQ-7
Microsoft 365 Word · controlled docs
W

Illustrative demo. The people, projects, issues, and documents shown are fictional, and citations are synthetic examples. Some integrations shown are still in development.

How it works

Regulatory compliance that keeps up with your code.

Cairn reviews regulatory evidence where your team already works and is built to keep your package current alongside it, so gaps surface early instead of at filing time.

Before

Long catch-up review meetings
Reconciling everything before a filing
One big compliance scramble

With Cairn

Flagged while the work is fresh
Docs that stay current as you go
A package built from your stack

Connect your tools

Cairn works where you do.

Cairn is built to review the code, docs, and tasks you connect and leave cited comments where your team works. GitHub pull-request review comes first; Google Docs, Jira, and Microsoft 365 review are still in development.

GitHub Pull request

example-device · PR #12

Document impact assessment is missing

Cairn · example rubric · pr_review.documentation_required
Google Docs Design doc

Intended Use & Indications

This intended-use claim needs a supporting clinical reference before it can be submitted.

Cairn · example citation · FDA guidance §IV
Jira Issue

DEMO board

This requirement has no verification evidence linked to it yet.

Cairn · example citation · requirement REQ-7
Microsoft 365 Word doc

Word · controlled docs

This section references a retired SOP revision — update to QMS-SOP-12 rev D.

Cairn · example citation · controlled-document index

Verified citations

Findings that show their work.

Cairn cites the guidance, rubric, and source artifact behind its flags, so reviewers can see why a flag matters before they act.

Hand-drawn tools connecting through flowing lines to a central source

Cited to the source

Flags link to the FDA guidance, device strategy, predicate device, or standard behind them — and the artifact Cairn reviewed.

Hand-drawn radar display with marked review points

Bounded by rubrics, not vibes

Checks run against versioned, inspectable rubrics — deterministic where they can be, judgment only where they must be.

Hand-drawn stack of reviewed documents with check marks

Replayable and auditable

Findings record the source version, rubric snapshot, and run that produced them, so you can re-run them or hand them to an auditor.

01 · Get started

Start where you are.

Whether you're just starting out or getting ready to file, Cairn slots into your existing tools and processes with no migrations or tedious onboarding.

Most teams Wire it into your stack Cited findings inside the tools you already use, and a readiness view that fills in as you connect sources.
Late-stage teams Close the pre-filing gap A cited readiness view, prioritized gaps, and in-tool comments your team can resolve before filing.
Greenfield Start a new device right A governed workspace set up so traceability and readiness can keep pace as the device takes shape.

02 · Stay in control

You stay in control.

Cairn automatically drafts, flags, cites, and prepares evidence, but every controlled decision stays with a human.

  • AI never signs, approves, or releases a controlled record.
  • Comments and changes are prepared for review, never pushed silently.
  • Your team can accept, edit, or waive every recommendation.
  • Submission packages stay in review until you choose to file.

03 · Track readiness

Know what's ready.

Cairn treats compliance the way your engineering team treats code quality — as something you can run, measure, and track. The score and checks shown are an illustrative example, not a real device's status.

78% ready
PASS Source mirror freshness — GitHub PR synced 4m ago
PASS Requirements trace to verification evidence 31 / 31
WARN Risk control rationale needs consultant review 2 cited gaps
HELD Jira task held for human review you decide

04 · File with confidence

File when you're ready.

Where Cairn is headed: automatic submission-package assembly and one-click filing, only after checks pass and the people accountable sign off. Both are future capabilities, not available today.

  1. Assemble the package

    Planned: Cairn compiles a cited, traceable submission bundle from the evidence it has been tracking, for your team to review.

  2. Review it together

    You and your consultant work through findings, waivers, and gaps in one place — no scavenger hunt across tools.

  3. File when you're confident

    Planned: submit to the FDA in one click, only once everything passes and the people accountable have signed off.

See Cairn in action.

Tell us about your device and your tools. We'll show you how Cairn can work for your team.

Request a demo