01 · Define
Describe the journey as code
Keep the flow key, steps, and variants alongside the product.
Visual review for the merge path
Merge with your eyes open.
Your tests can be green while the product is broken. Reshot captures critical flows from the real app, shows what changed, and makes a named reviewer decide before it merges.
How it works
Define flows. Capture every change. Block the break.
A Flow is one critical journey. Its contexts are captured together, reviewed in one PR-native workspace, and billed as one unit.
02 · Capture
Run it in CI
Reshot captures the contexts your team actually needs to trust.
03 · Decide
Review the evidence
Approve or reject the visual change with an attributable decision.
reshot.config.json
{
"scenarios": [{
"key": "checkout",
"steps": [{ "action": "screenshot", "key": "checkout" }]
}]
}The problem
AI ships faster than you can look.
Your test suite is blind to the screen. The states that break are the ones no one checks by hand: admin and member, dark mode, German, empty data, and their combinations.
Tests green · UI broken
Capture the real screen for every important context before a pull request becomes a release.
Why Reshot
Verify complete authenticated flows, not isolated components.
Reshot owns the context matrix, visual diff, review decision, required status gate, audit trail, and always-fresh approved result.
Real auth, real data states
Run against localhost or your CI environment with the accounts and fixtures your team trusts.
One PR-native decision
Every changed flow and context is grouped under the commit that caused it.
Human judgment where it matters
Product, design, QA, or engineering approve from the dashboard. Invite them free — no GitHub seat required.
Agents · beta
Give coding agents visual evidence.
Agents can inspect the same flow matrix and diffs before a person reviews the pull request. Human approval stays the final governance boundary.
Agent review queue
checkout · admin · dark — agent changed navigation · awaiting approval
settings · member · de-DE — before and after ready
onboarding · empty state — required check passed · audit event recorded
Governance
Automation gathers evidence. People own the decision.
Keep an immutable decision trail for every visual change and release. Mask PII and run captures in infrastructure you control. If policy requires assets to stay in your own bucket, bring-your-own-storage is a storage-only path — it replaces the hosted review queue and version history rather than adding to them.
- Real authenticated product flows
- Every role, theme, locale, and data state
- Named approval before a change ships
Start with one flow
Stop merging blind.
Free on your CI in minutes. Start with one critical flow and see every role, theme, locale, and data state before it ships.