Now in early access

Your docs know
nothing about your code.

Exodocs connects your code repositories to your documentation hub and alerts your team the moment a page drifts from the systems it describes. No more discovering stale docs when it matters most.

Request early access See how it works →

Free for up to 3 pages · No credit card required

app.exodocs.dev/app
🟢 Fresh
11
score ≥ 80
🟠 Stale
5
needs review
🔴 Critical
2
alerts sent
Tracked pages — sorted by freshness
34
Auth Service Overview
acme/api-service · 2 mappings
Critical
51
Payments API Overview
acme/payments · 3 mappings
Stale
63
Onboarding Checklist
acme/web-app · 1 mapping
Review
90
Deployment Guide
acme/infra · 4 mappings
Fresh
100
Database Schema
acme/api-service · 2 mappings
Fresh
Active alerts
Auth Service Overview
Score 34 · charge() method removed in commit a3f7b2c · The PaymentsService now uses confirm() from Stripe v2
Review doc ↗
Payments API Overview
Score 51 · 3 files changed in app/services/payments/**
Review doc ↗

Works with your stack, not a fixed one.

Exodocs is built around the concept of a code repository and a documentation hub — not specific products. We're starting with the most common pair and expanding from there.

Available now
GitHub
Code repository · push webhooks & commit metadata
Notion
Documentation hub · page reads, freshness tracking
Slack
Alerts & notifications · incoming webhook delivery
On the roadmap
GitLab
Code repository
Soon
Confluence
Documentation hub
Soon
Linear & Jira
Issue tracking · auto-create drift tickets
Soon
Microsoft Teams
Alerts & notifications
Soon

Using a different tool? Tell us what you need →

Code moves fast.
Your docs don't know.

Your team writes excellent documentation. Then six months later, the service it describes has been refactored, renamed, or replaced — and nobody updated the page.

01 — Incidents

Stale procedure docs cost 20+ minutes when it matters most

Your on-call engineer opens the Auth Service overview. The procedure references a service that was rewritten three months ago. The incident drags on while they reverse-engineer the current behaviour.

02 — Onboarding

New hires learn the old way, not the current way

The onboarding guide describes a deployment process that changed twice since it was written. New engineers spend weeks building a mental model based on documentation that no longer reflects reality.

03 — Trust

Once engineers stop trusting docs, they stop reading them

A single misleading page at the wrong moment destroys confidence in all documentation. Teams start ignoring their knowledge base entirely and fall back to asking colleagues directly — creating a bottleneck that doesn't scale.

"
Developers spend 3–10 hours per week searching for answers that should already be documented. Teams with stale internal documentation lose an average of 20+ minutes per P1 incident following outdated procedures.
— GetDX Engineering Productivity Study, 2025

Set up in 10 minutes.
Alerts in your inbox the same day.

1

Connect your code repositories

Add a webhook to any repository. Exodocs receives push events and extracts the file paths that changed. No code access required — just file paths and commit metadata.

2

Link documentation pages to code areas

Tell Exodocs which pages in your documentation hub describe which parts of your codebase — manually or with AI-powered mapping suggestions. One page can map to multiple file patterns like app/services/auth/**.

3

Get alerts when drift is detected

When code that a documentation page describes changes, that page's freshness score drops. When it crosses your threshold, Exodocs sends an alert with the commit, the matched files, and an AI summary of what likely needs updating.

4

Update the page, score resets to 100

Edit the page in your documentation hub. Exodocs detects the update, resets the freshness score, and clears the alert. The cycle starts fresh. No manual bookkeeping.

🔒 #eng-alerts · Exodocs
🤖
Exodocs Today at 2:47 PM
🟠 Auth Service Overview may be stale — score dropped to 51/100
Auth Service Overview
Commit refactor: migrate to Stripe v2
By @jsmith
Files app/services/payments_service.rb
The charge() method referenced in this page was removed. PaymentsService now uses PaymentIntents.confirm(). The "Initiating a Charge" section likely needs updating.
📄 Open doc
Not relevant

Everything a serious team needs to keep docs current.

Freshness scoring

Every tracked documentation page gets a score from 0–100. It decays when matched commits arrive and resets to 100 when the page is edited. Visual and unmissable.

Slack alerts with context

Alerts include the commit message, author, matched files, and an AI-generated summary of what changed — so the page owner can update without reading the diff.

AI mapping suggestions

Exodocs analyses your documentation page content and your repository file tree and suggests which code paths the page likely describes. Review and accept in one click.

Semantic scoring

Not every commit is relevant. Before applying score decay, Exodocs rates how semantically relevant the commit is to the page content. Whitespace fixes don't penalise your docs.

Drift summaries

AI-generated 2–4 sentence plain-English explanations of what changed and which section of the doc likely needs updating. Written for the doc owner, not the engineer who wrote the code.

Team roles & invitations

Owners, admins, and members with role-based access control. Invite teammates by email — they set their own password and join your organisation immediately.

Built for teams who ship fast and document seriously.

📊

Engineering managers & tech leads

A single dashboard showing the freshness of every critical doc across your team. Catch rot before it causes an incident or embarrasses a new hire.

🛠️

Senior engineers & service owners

Get a targeted alert when code you wrote is described in a documentation page that has gone stale — with context on exactly what changed, so you can fix it in minutes.

🚨

SREs & on-call engineers

Procedure docs and architecture pages flagged before incident response. No more discovering mid-incident that a page references a service deprecated six months ago.

🌱

New hires & growing teams

Indirect but powerful: the setup guides, architecture docs, and onboarding pages a new hire follows are more likely to reflect reality. Ramp time decreases when documentation can be trusted.

Start free. Pay when it's valuable.

No credit card required to start. Upgrade when Exodocs has saved your team from a costly stale-doc moment — or when you want to track more pages.

Free
$0/month
Forever free · no card required

Up to 3 documentation pages
1 code repository
Freshness scoring
Slack alerts
AI mapping suggestions
Drift summaries
Team members
Get started free
Growth
$99/month
Per organisation · billed monthly

Unlimited pages & repos
AI drift summaries
Inline doc annotations
Full team access
Drift history timeline
Priority support
Health reports (coming soon)
Issue tracker integration (soon)
Join waitlist

Built with security-first engineering teams in mind.

You're connecting tools that touch your codebase and your internal documentation. We take that seriously. Your tokens are encrypted at rest, your code is never stored, and you can turn off every AI feature if you prefer.

Read our full security page →

AES-256 encryption

All tokens encrypted at rest. Database dumps reveal only ciphertext.

Read-only access

We never write to your repositories or documentation pages without explicit opt-in.

No code stored

File paths and commit metadata only. Source code is never persisted.

Tenant isolation

Row-level isolation. No org can ever access another's data.

Early access · limited spots

Stop finding out your docs
are wrong when it matters most.

Join the waitlist. We're onboarding design partners now — free access for 3 months in exchange for weekly feedback.

We'll reply within 24 hours. No spam, ever.