DocsUpdater

Documentation that follows the product

The open source agent that turns pull requests into help docs for your customers

DocsUpdater reads a GitHub pull request and your existing help docs, opens your staging or production app, and creates a Markdown draft with fresh screenshots.

Review everything before publishing. DocsUpdater never changes your repositories.

Analyze your first PR freeSee an example result

10 PR analyses free every month. Open-source engine. Read-only GitHub access.

Example DocsUpdater result

acme/product-app #184

Add notification scheduling

Completed

Documentation impact

  • help-center/notifications.md

    States that notifications are always delivered immediately. The pull request adds a daily summary and a delivery window, so this section needs to be updated.

  • help-center/roles-and-permissions.md

    The Viewer row of the permissions table does not mention notification settings, which members of every role can now change for themselves.

Documentation draft

help-center/notifications.md
## Choose when notifications arrive

Notifications are delivered immediately by default. To collect them into a
single message instead:

1. Open **Settings → Notifications**.
2. Turn on **Daily summary**.
3. Choose the delivery days and time.

Members can change their own schedule. Only workspace owners can change the
default that applies to new members.

![Notification schedule controls](screenshots/notification-schedule.png)

Screenshots

notification-schedule.png
delivery-window.png

Why teams use it

Stale documentation, caught on the pull request.

Find the pages that just went stale

Every run compares one pull request against the help documentation you already have, and names the files that no longer describe the product.

Screenshots from your own app

DocsUpdater opens your staging or production app, signs in with a test account when needed, and captures the screens your docs reference.

Markdown that fits your docs

Drafts follow the structure and file layout of your existing documentation, so they are ready for your team to review.

Ready for your publishing workflow

Copy the Markdown, download the screenshots, and publish with the tools and review process your team already uses.

How it works

How DocsUpdater works.

Set up a project once, then analyze any pull request in a click.

  1. 01

    Connect your project

    Choose the product repository, the documentation repository and branch, and a reachable URL for your app. Add a dedicated test account if the pages you document require signing in.

  2. 02

    Choose a pull request

    Pick any open or merged pull request and run it on demand, or turn on automatic runs so a merge starts one for you.

  3. 03

    Review the proposed update

    You get a docs impact report, a Markdown draft, and the screenshots it references. Copy the Markdown, download the screenshots, and publish through the workflow you already use.

Works with

Built for web products documented in GitHub.

Fits your existing publishing workflow

Review the Markdown and screenshots, then publish with the tools your team already uses. For protected pages, use a dedicated test account; SSO, CAPTCHA, and two-factor prompts may require a staging environment.

Open source

Use the hosted version or run it yourself.

DocsUpdater is the hosted version of Screenshot Agents, the open-source engine behind its pull-request analysis and screenshot workflow.

Hosted

Ready to use with DocsUpdater.

Connect your repositories and run your first analysis without managing Docker, model credentials, or your own GitHub App.

Start with DocsUpdater

Open source

Your infrastructure, your configuration.

Bring Docker, a GitHub App, and OpenAI or Azure credentials. Audit the code, adapt the workflow, and run it on infrastructure you control.

View source on GitHub →

GitHub access

Read-only, on the repositories you choose.

  1. 01

    Sign in with GitHub

    Create your DocsUpdater account. Signing in does not grant access to any repositories.

  2. 02

    Install the GitHub App

    Choose the repositories DocsUpdater can read. It cannot modify code, create commits, push branches, or publish documentation.

Repository access is read-only

The GitHub App reads the contents and pull requests of the repositories you select. It does not request write permission to any of them.

You control what gets published

DocsUpdater prepares private drafts for review. You choose what to publish and when.

Results stay private to you

Only you can access the drafts, impact reports, and screenshots created for your projects.

Test credentials are protected

Optional test-account passwords are encrypted at rest and kept out of generated instructions and results.

Full security details →

Pricing

Open source or hosted. Start free either way.

Run it yourself for free, or choose a hosted plan with the infrastructure already handled.

Open source

Open source — Free

Unlimited runs

Run Screenshot Agents on your own infrastructure with your own model credentials.

View source

Hobby

Hobby — Free

3 PR analyses per month10 PR analyses per month for a limited time

Enough to try the whole workflow on a real pull request.

Start free

Startup

Startup — $20 / month

25 PR analyses per month

For a team shipping product changes every week.

Choose Startup

Enterprise

Enterprise — $100 / month

120 PR analyses per month

For teams shipping across several projects.

Choose Enterprise

How hosted usage works. One run analyzes one pull request. Manual runs and automatic runs after a merge each use one run, and so does a retry. Hosted limits reset monthly, and paid plans can be canceled at any time from the billing page.

FAQ

Questions, answered.

Where does my documentation need to live?

In a GitHub repository DocsUpdater can read — either the product repository or a separate one, on the branch you choose. If your help center lives only in Notion, Zendesk, or Intercom, DocsUpdater cannot read or update it today.

Can I analyze a pull request before it is merged?

Yes. A manual run works on any open or merged pull request in the product repository. Optional automatic runs can start after a merge.

Does DocsUpdater publish or commit anything?

No. It prepares a draft for review. It cannot commit files, push branches, open pull requests, or publish to a documentation platform.

What GitHub permissions does it request?

The GitHub App asks for read-only access to contents and pull requests, on the repositories you pick during installation. If you turn on automatic runs, it also subscribes to pull-request webhooks for those repositories.

What counts as one run?

One run analyzes one pull request and produces one result. A manual run and an automatic run after a merge each use one run from your monthly total.

Do failed runs and retries count?

Today every queued run counts, including a retry after a failure. If a run fails because of a problem on our side rather than your configuration, email support@docsupdater.com and we will credit it back.

How long are results kept?

Drafts, reports, and screenshots stay in your account until you ask us to remove them. There is no self-serve delete yet, so email support@docsupdater.com and we will delete a project's history.

Which sign-in flows does DocsUpdater support?

Standard username-and-password forms work best with a dedicated test account. SSO, CAPTCHA, and two-factor prompts may require a staging environment or a prepared session.

Can teammates share a project?

Not yet. Projects and their runs belong to the GitHub account that created them, and there are no shared workspaces or roles.

DocsUpdater

Stop discovering stale documentation after your customers do.

Analyze your first PR free

Read-only GitHub access. Review and publish through your existing workflow.