Ellie Docs is an AI-maintained help centre. Point it at your app, your codebase, or your existing help content, and it drafts articles, keeps them accurate as your product changes, and answers customers directly — so your docs stop being the thing everyone means to update. If your product has an API, it writes and maintains the reference for that too.
Invites go out in small batches — tell us what you're building and we'll prioritise the people we can help first.
Early access · no spam, ever · we'll email you the moment it's ready
Ellie's own help centre runs on Ellie Docs. help.tryellie.com is built, illustrated and kept current by the product on this page — go and read it before you decide.
A feature ships, a button moves, an API field gets renamed — and the help article stays exactly as it was, quietly wrong, until a customer notices. Ellie Docs closes that loop.
Connect a GitHub repo and Ellie checks out your code, maps your routes and features, and works out what your product is actually for. It runs your app in a sandbox and captures real screenshots — so articles show your product, not stock imagery.
Already have articles in Intercom, Zendesk, GitBook, Notion — or scattered across a wiki? Point Ellie at your current help centre and everything comes in as drafts: organised, editable, and ready to improve. You start from what you've already written, not from a blank page.
Published articles go live on a fast, searchable help site with full-text search and grounded Ask-AI answers — hosted by Ellie, served on your own domain, no second docs tool to run.
Every article opens in a proper editor with sections, callouts, images and videos. Or skip the editor entirely: chat to Ellie, tell it what shipped, and review the draft it writes. Articles stay grounded in your code, so Ellie knows which ones a change affects.
Every push is judged against your published articles. When a change makes one wrong, Ellie flags it with the evidence and drafts the fix for your review.
Ellie runs your app and captures authenticated screenshots for articles — and recaptures them when your UI changes, so images never show a product that no longer exists.
Your help centre ships with grounded Ask-AI answers from your published docs — and if you also use Ellie Desk, resolved tickets flow back into new articles.
Alongside your help centre, Ellie Docs publishes a full API reference — every endpoint, its parameters, its responses and a worked example, on the same domain and the same search. And you don't need to have written an OpenAPI spec to get one.
Ellie reads your OpenAPI file from the repo — or from a URL — resolves it, and writes the part
a spec never contains: plain-English narrative for every operation, and examples in your own
domain language instead of string and foo. Every example is checked
against the endpoint's own schema before it's published.
It reads your router to find every endpoint, mines your request validators for the real field types, and where the code still doesn't say, an AI investigator reads the handler itself — and has to cite the lines it took each field from. Anything it can't evidence is recorded as a gap, not invented.
Each operation is labelled with where it came from — read from your spec, mined from your validators, or investigated in your code — so you know at a glance what's solid and what deserves a second look.
Endpoints Ellie finds in your code stay internal until you publish them. Your admin routes don't end up in your public reference because a scan found them.
When an endpoint changes shape, Ellie diffs it against the last version, marks what's breaking, and publishes the entry. Endpoints you shipped but never documented get flagged too.
You didn't write the code by hand — you shouldn't have to write the docs by hand either. Ellie Docs generates a real help centre from your live app, no engineering time required.
See how → FOR ENGINEERING TEAMSEllie Docs connects to your GitHub repo, flags articles a merged PR just made stale, and drafts the fix — so documentation stops rotting the moment nobody's looking.
See how →We're bringing waitlist signups on in small batches. Join now and we'll email you when it's your turn — once you're in, connecting a repo gets your first drafts ready to review in minutes.
No. If you built with a tool like Lovable, Bolt, or v0, Ellie Docs works from your live app and existing content — see the vibe-coded-apps page for specifics.
Yes — Ellie Docs hosts and renders your public help centre directly, on your own domain, so you're not maintaining a second, separate docs tool. Your existing articles import as drafts.
Connecting a repo gets your first drafts ready to review in minutes, not days — you're editing real articles about your own product in your first sitting, not staring at an empty workspace.
Yes. Ellie Docs publishes an API reference next to your help centre, on the same domain. If you have an OpenAPI spec it reads that; if you don't, it derives one from your code and labels where each detail came from. Endpoints it finds itself stay private until you publish them.
Nothing goes live on its own — Ellie drafts, you review and publish. Before a draft even reaches you it runs through an automated quality gate that checks it against the code it documents, and API examples are validated against the endpoint's own schema, so an example that doesn't fit is dropped rather than shipped.
We don't retain a copy of your repository — code is fetched from GitHub when Ellie needs to look at it, and re-fetched by commit later rather than kept. What's stored is the derived material an article stands on: the excerpts and citations behind each claim, so you can always check Ellie's working. Secrets found in files are redacted before anything is stored, your code is never shown to your readers, and it's never used to train models.
No — Ellie Docs is a separate, standalone product you can use with or without Ellie's original email assistant. It does share the same underlying AI.
