Documentation drift detection

Your docs are lying.

fetherdok continuously monitors your codebase and tells you exactly where your documentation has fallen out of sync — before it causes an incident.

Join the Waitlist See how it works ↓
fetherdok — drift report — 3 issues found
⚠ critical README.md → auth section
Code switched from JWT to session-based auth 3 weeks ago. Documentation still describes JWT flow.
⚠ high /docs/api.md → payments endpoint
Endpoint now requires idempotency_key header. API docs don't mention it.
ℹ medium /docs/deploy.md
References docker-compose.yml — deleted 2 months ago. Deployment now uses Kubernetes manifests.

The problem

Code moves fast.
Docs don't.

Onboarding disasters

New hires follow your setup guide. It's wrong. They break staging on day one. Sound familiar?

Invisible API changes

Your payment endpoint added a required header 3 PRs ago. Your API docs still show the old contract. Your integration partners are about to find out the hard way.

Tribal knowledge

The only person who knows the deployment process is on holiday. The runbook references infrastructure you decommissioned in January.

How it works

Connect. Scan. Fix.

Step 01

Connect your repo

One-click GitHub App install. Read-only access. 30 seconds.

github.com
Install fetherdok
✓ Read-only access to code ✓ Read-only access to docs ✓ No write permissions needed
Step 02

Get your drift report

fetherdok maps your codebase against your documentation and surfaces every place they disagree. Critical drifts first.

drift-report.txt
⚠ critical README.md → auth section
⚠ high /docs/api.md → payments
ℹ medium /docs/deploy.md
✓ ok 14 docs in sync
Step 03

Fix with one click

For every drift, fetherdok generates a documentation update and opens a PR. Review, tweak, merge. Back to building.

docs/api.md — proposed fix
docs/api.md
## POST /api/payments
### Headers
- Authorization: Bearer <token>
+ Authorization: Bearer <token>
+ Idempotency-Key: <unique-key>
### Request Body

Always watching

Drift doesn't sleep.
Neither does fetherdok.

On every push to main, fetherdok re-scans and catches new drift the moment it appears. Weekly digest shows what's falling behind.

No cron jobs to set up. No manual audits. Just connect and forget.

<30s scan time per push
0 config required
Activity — this week
Mon ✓ 2 drifts detected → auto-fix PRs opened
Tue ✓ PR #42 merged — API docs updated
Wed ✓ Clean scan — all docs in sync
Thu ✓ Deploy guide updated after infra change
Fri ⚠ 1 new drift — deployment guide references removed service

Early access

Stop shipping lies.

Join the waitlist. First 100 teams get free access during beta.

No spam. Just a ping when we're ready.