See every change,
right in the PR.
DemoBot is a GitHub-native AI agent that runs your pull request, captures real screenshots of what changed, and posts them inline in the PR. Reviewers see the change at a glance, no branch checkout or preview clicking required.
Works with all modern web stacks
Reviewing a PR shouldn't mean guessing what it does.
Seeing a visual change today means checking out the branch and running it. Or digging through a preview deploy to find what moved. DemoBot does that for you. Screenshots of every change land right in the PR.
Install & pick repos
Add the GitHub App and choose the repositories you want covered. DemoBot detects your framework.
Open a pull request
DemoBot spins up your app from the branch, reads the diff, and captures real screenshots of the views your changes touch.
Review in the PR
The screenshots and demo summary post as an inline PR comment. Everyone reviewing sees the change where they already work.
Everything a review needs, on autopilot
One agent runs the app, captures the screens, and explains the change.
Zero config
DemoBot detects your framework and infers the build and run steps. Add a test login or secrets when your app needs them.
Real screenshots, not guesses
DemoBot runs your actual branch and photographs the real UI. These are true screenshots of your running app, never AI generated mock pages.
Demo Summary
Plain-English summary of what changed and why, written from the diff and the captured screens.
Right in the pull request
Screenshots and the summary post as an inline PR comment.
Fresh on every push
Push a new commit and DemoBot re-captures the affected screens, so the PR always reflects the current state of the branch.
Framework-agnostic
If it builds and runs, DemoBot can capture it: Next, Vite, Remix, Nuxt, SvelteKit, Astro, and more.
Everyone on the PR sees the change
The screenshots show up right where your team already reviews.
Engineers
Review behavior alongside the diff and catch unintended UI changes without checking out the branch or running it locally.
Product managers
Sign off on the real thing in the PR before merge.
Design & QA
Check the implementation against the spec on every branch, screen by screen, straight from the PR.
Open-source maintainers
See what a contributor's PR actually does before checking out an unfamiliar fork.
Priced by usage, not seats
Every plan includes screenshots and AI summaries in your PRs. A demo is one capture run on a pull request.
Enterprise
Negotiated demo limits, SSO & audit logs, on-prem runners, and SLA support for orgs at scale.
Questions
How is this different from deploy previews?+
Preview deploys (such as Vercel's) give you a full deployment of the change — but you still have to open it and click around to find what's different. DemoBot shows those changes directly in the PR as screenshots, so you can review at a glance without spending time navigating the preview environment.
Do I need to change my codebase?+
Usually not — DemoBot detects your framework and infers the build and run steps. A few cases need a hand from you: apps that gate most functionality behind login (provide test-user credentials), apps that need secrets not checked into the repo (add them to DemoBot's secrets manager), and apps that depend on local infrastructure not documented in the repo (e.g. a local Postgres), which may need a little config or documentation so DemoBot knows how to run them.
How does it handle databases and secrets?+
That's up to your app. DemoBot runs your code as-is, so it talks to whatever databases and services your branch is configured to use — we don't provision or dictate your data layer. You supply any secrets or connection details through DemoBot's secrets manager.
Is my source code safe?+
Yes. DemoBot runs in AWS Lambda MicroVMs. VMs are snapshotted to support continuation; snapshots are saved in secure S3 storage and expired after 30 days.