Keep your docs in sync with your code, automatically.
You ship code faster than anyone can maintain the docs. uptodate reads every change you merge to GitHub, finds the documentation it made wrong, and opens a pull request with the fix.
Built for software teams whose product or API docs change every week and never quite keep up.
From merged code to corrected docs.
No dashboard to babysit and no new writing habit to build. It runs on the changes you already ship.
Connect a repo
Point uptodate at a GitHub repository and the folder that holds its docs. Setup takes a couple of minutes.
It reads what you merge
Every code change is compared against your docs. uptodate finds the exact pages a change made inaccurate.
It drafts the fix
Not a vague suggestion. The precise line-level edit, written in your docs' own voice, with the reason for each change.
You review a PR
The edits arrive as a normal pull request. Read the diff, merge it, and your published docs update the moment you do.
One place to see every doc it touched.
Each run shows what you merged, which pages it changed, and where the pull request landed. Nothing happens without you seeing it.
It writes to the docs you already publish.
uptodate opens a pull request against your docs in GitHub. Since GitBook, Mintlify, and ReadMe sync from git, your published site updates the moment you merge.
Stop shipping features faster than your docs.
Connect your first repository and I will help you get set up.