UI Verify
UI Verify provides visual regression testing for Playwright, Storybook, Vitest and Bun, helping development teams and coding agents catch unintended UI changes before they merge. It captures UI states, compares them with baselines, uses an AI judge to distinguish intended changes from regressions, and reports the result back to pull requests.
At a Glance
- Frontend development teams
- Product and QA teams shipping web applications
- Teams using coding agents such as Claude Code, Cursor or Codex
- Open-source projects
- +2 more
AI Tools by UI Verify
(1)UI Verify
AI Visual Regression Testing
Discussions
No discussions yet
Be the first to start a discussion about UI Verify
Latest News
Published 'Playwright MCP: what your coding agent sees and misses,' covering agent browser access and the visual changes accessibility snapshots can miss.
Published 'Before and after screenshots in every pull request,' describing automated screenshot-based PR review.
Published an Angular visual-regression-testing guide showing Vitest browser mode and TestBed capture.
Published guidance on handling dynamic content in visual tests with fixtures, masks and agent review.
Products & Services
Cloud service that captures Storybook, Playwright, Vitest, Bun or uploaded PNG states, compares them with versioned baselines, runs AI review, and posts GitHub pull-request checks and comments.
Open-source command-line uploader and local checker. It uploads Storybook builds, Playwright/Vitest/Bun archives or finished screenshots; uiverify check renders selected targets against the CI baseline without posting a PR check or moving the main baseline.
Playwright capture SDK that archives the final UI state of existing tests for cloud replay and visual diffing.
Vitest browser-mode capture plugin; it archives rendered DOM/resource state and supports named snapshots via takeSnapshot().
Market Position
UI Verify positions itself against visual-testing services such as Chromatic, Percy, Applitools and Argos. Its differentiation is an AI judge that interprets intent rather than only reporting pixel deltas, deterministic cloud/archive-replay capture, snapshot-only-what-changed billing, and an MCP loop designed for coding agents. Its public site compares pricing and features with those competitors.
Leadership
Founders
Igor Luchenkov
Founder/building UI Verify; Staff Engineer at Clarify (clarify.ai). His public GitHub profile also associates him with Iteratively, and he has published the UI Verify technical blog under his name.
Executive Team
Igor Luchenkov
Founder
Staff Engineer at Clarify; public profiles also associate him with Iteratively. He writes and maintains UI Verify's product and technical materials.
Founding Story
UI Verify was created to address the gap left by hand-rolled visual-testing setups for coding agents. Its founder describes teams assembling screenshots, baselines, deterministic capture, cloud rendering, diff review and agent access themselves; UI Verify packages those hard parts into a hosted product with an AI verdict and MCP-based agent loop.
Business Model
Revenue Model
Monthly SaaS subscriptions based on included monthly snapshot and AI-review quotas, with metered snapshot overage; Enterprise adds volume pricing, annual/invoice contracts and custom retention/security terms.
Pricing Tiers
10,000 snapshots and 100 AI reviews per month; includes snapshot-only-what-changed, browser support for Storybook, hosted Storybook, MCP, unlimited projects/members and GitHub PR checks/comments.
30,000 snapshots and 1,000 AI reviews per month; $0.004 per snapshot beyond the plan.
65,000 snapshots and 2,500 AI reviews per month; $0.004 per snapshot beyond the plan.
Volume snapshot pricing, invoice billing/annual contracts, SAML SSO, SCIM, custom retention/DPA, SLA and priority support.
Target Markets
- Frontend development teams
- Product and QA teams shipping web applications
- Teams using coding agents such as Claude Code, Cursor or Codex
- Open-source projects
- Teams using Storybook, Playwright, Vitest or Bun
- Mobile/native/React Native teams that already produce screenshots
- Visual regression checks on every GitHub pull request
- Pre-push/local checks while a coding agent edits UI
- Storybook component and page visual testing
- Playwright end-to-end visual testing without adding snapshot calls
- Vitest browser-mode component visual tests
- Bun browser visual tests
- JetBrains
- ChatJS
- Cura
- Metica