Your product changes every day. Now your help docs can too.

Driftless watches your app for changes. It tells you which articles just went stale, and which ones you're missing entirely. Then it drafts the fix and a fresh screenshot for you to approve.

Request early access How it works
An App update card listing four proposed help center updates with a Review updates button, and the agent’s queue of running tasks overlapping it.

Docs don't get outdated all at once. They drift.

A button gets renamed. A setting moves one menu over. A step disappears. No single change is worth a full docs review, so none of them get one, and a year later half your help center describes a product that doesn't exist anymore. The first person to notice is a customer, and the way they notice is by filing a ticket.

Docs used to be a chore.
Now they update automatically when you ship.

Acme app Projects screen captured on desktop in light mode.

Screenshots that maintain themselves

Desktop, tablet and phone, light and dark, captured from a plain-language description. After a redesign, recapture is automatic.

Voice settings: Reads as Friendly, Contractions yes, four writing rules, and an uploaded style guide marked In use.

Drafts in your voice

It works from your code, a running copy of your app, your existing articles and how your team writes. Every sentence you rewrite is a correction it carries forward.

A ranked list titled What to write next: Export data to CSV, Usage dashboard, Export a report as PDF, each with a ticket count and a Draft button.

Know what to write next

It reads your codebase, help center and support threads, then ranks the gaps. The feature that shipped three releases ago and never got an article comes first, with a draft attached.

A proposed help center update list: four articles flagged after a merge, each with the kind of change and a Review updates button.

Every merge gets read

Driftless monitors your app for changes and knows exactly which help article covers which part of your app. When a change is made, Driftless knows exactly which articles need updates.

You approve every word.

The Driftless review board: an inbox of flagged articles on the left, and the Invite a teammate article on the right with a current-versus-proposed screenshot and a rewritten step.

Every drift alert, draft, and new capture lands on one review board. See the change side by side with what's live, edit inline, approve. Batch a release's worth of updates into a single review instead of a dozen interruptions.

Three steps. You stay in control of all of them.

  1. 01

    Point it at your app.

    Connect your repository and a login for a test copy of your app. Driftless maps which articles describe which parts of the product, and starts watching.

  2. 02

    It drafts the updates.

    Each change folds into the article that already covers it, copy and screenshots both. Rewrite a sentence and the correction carries into the next draft.

  3. 03

    You review and publish.

    Everything lands on one board. See the change side by side with what's live, tweak inline, approve.

What it means for your team

  • Support and success

    Fewer tickets that were never really questions. The articles match what the customer is looking at.

  • Product

    Documentation is ready the moment the feature is. Captures and drafts run against a test copy before launch.

  • Technical writers

    Renamed buttons, re-cropped screenshots, moved settings stop being your week. What's left is the work that needed a writer.

  • Small teams without a writer

    The list you never had time to make: what is broken, what is missing, and a draft of each.

Give your AI assistant a help center it can trust.

If you run an AI assistant in your product, it answers from your docs. Keep those current and it gives confident, correct answers. Let them drift and it gives confident wrong ones, at scale, to customers who have no way to tell. Driftless keeps the source current against the code itself.

We're building this now.

Early access is opening to teams whose product moves faster than their documentation. Tell us what you're running and we'll be in touch.

Early access only. We read every reply and will not share your address.