FOR ENGINEERING TEAMS

Docs that know when your code changed.

Every docs tool can host an article. None of them know when a merged PR just made it wrong. Ellie Docs connects to your GitHub repo, tracks the code each article actually depends on, and flags — then drafts — the fix the moment it goes stale.

Early access · no spam, ever · we'll email you the moment it's ready

WHY DOCS ROT

Nobody's job is "notice the docs are wrong."

A field gets renamed in the API. An endpoint gets deprecated. A UI flow gets redesigned. The PR merges clean, tests pass, and the help article referencing the old behaviour sits there — correct-looking, silently wrong — until a customer or a support ticket catches it.

🔗

Code-linked articles

Each article can be tied to the code, endpoints, or API spec it actually documents — so Ellie Docs knows exactly what to watch.

🚨

Staleness detection on merge

A GitHub App watches merged PRs, judges whether they affect a linked article, and flags it — with a drafted revision ready for review, not just a red banner.

📘

API reference from your spec

Generate and keep API documentation in sync directly from your OpenAPI spec, diffed against the previous version on every change.

HOW IT WORKS

Connect once. Docs stay honest from then on.

1

Connect your repo

Install the Ellie Docs GitHub App on the repos your product docs depend on. Code access is ephemeral — pulled to derive metadata, then discarded, never stored.

2

Import or crawl your docs

Bring existing docs in via crawl-import, or start fresh — Ellie Docs drafts articles and links each one to the code, endpoints, or spec it depends on.

3

Review, don't chase

When a merge affects a linked article, Ellie flags it and drafts the revision. Your team reviews a queue of proposed fixes instead of hunting for what broke.

FAQ

Engineering-team FAQ

What repo access does this need?

A GitHub App scoped to the repos you choose. Code is pulled ephemerally to derive documentation-relevant metadata — never stored long-term, never used to train models.

Does this replace our existing docs tool?

Yes, that's the intent — Ellie Docs hosts and renders the public help centre directly, including custom domains, so you're not running two systems in parallel.

Can we generate API reference from our OpenAPI spec?

Yes — point Ellie Docs at your spec and it generates and maintains reference docs from it, diffed against each new version as your API evolves.

What if we also run customer support?

Pair Ellie Docs with Ellie Desk (also in early access): resolved support tickets can become new doc articles in one click, and Desk's AI drafts get grounded in your published docs automatically.

Stop finding out from a support ticket.

No spam. Just one email when your access is ready.

Early access · no spam, ever · we'll email you the moment it's ready

Building on Lovable, Bolt, or v0 instead? See Ellie Docs for vibe-coded apps →