Show HN: Vizzly – Visual testing platform with built-in review workflows

Hey HN! I’m Robert. I worked on [Percy’s SDKs/support from 2018–2022.](https://github.com/percy/cli/graphs/contributors) If you ever reached out to support or opened an issue, I probably helped you. Hopefully it was positive :) After a few years away, visual testing still felt stuck, so I'm building Vizzly.

The problem: Design handoffs kinda suck. Designers make beautiful specs, devs implement them, then everyone realizes the details got lost somewhere. Current visual testing tools catch broken CSS but miss the real issue - making sure what ships actually matches what was designed, functionally (like really in the browser/OS/etc).

What it is

- Visual testing + review where you send actual screenshots (not DOM re-renders). Can be _any_ image to review (PDFS!)

- Collaboration built-in: reviewer assignment, approvals, @mentions, screenshot-level threads.

- Baselines: automatic (Git-aware), manual (not Git-based), or hybrid.

- Team-based pricing; generous free plan for OSS; on-prem available.

What’s different

- Capture-first: use the pixels your app produced (no “but it doesn’t look like that on my machine/CI”).

- Local TDD + CI parity: run locally with instant feedback; same flow in CI.

- Custom properties to filter/slice reviews (component, viewport, theme, etc).

Try it quickly (Playwright example)

```

npm i -D @vizzly-testing/cli

export VIZZLY_TOKEN=your-token

# in your tests:

import { vizzlyScreenshot } from '@vizzly-testing/cli';

let img = await page.screenshot({ fullPage: true });

await vizzlyScreenshot('homepage-layout', img);

```

I would love feedback on everything! Rough edges you hit using the product/sdk, baseline expectations across branches, what you need for design/dev review to feel “done”, etc. Features like root cause analysis, an MCP, and more collab features are coming. But it's just me building :p

I'm a big fan of OSS, so the OSS plan is pretty generous (10 seats + 10 review seats (20 total), unlimited public projects, 75GB, 6 concurrent builds). If it's not generous enough for teams, I'm willing to up it!

This is my first time launching anything like this, I'm super keen on getting feedback and working any support or suggestions folks have. If anyone knew me from my support at Percy, I _really_ enjoy those conversations and opportunities to ship a fix or feature at the end of a chat. If Vizzly isn't it for your team, I wanna know why and what I can do to help you.

Backstory + screenshots from my intro blog post: https://robertdelu.ca/2025/09/07/vizzly-introduction