Show HN: Vizzly – Visual testing platform with built-in review workflows
Show HN (score: 6)Description
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
More from Show
Show HN: Opal Editor, free Obsidian alternative for markdown and site publishing
Show HN: Opal Editor, free Obsidian alternative for markdown and site publishing A fully featured markdown editor and publisher. Free, open-source and browser-first (no backend required). Built with modern technologies like React, TypeScript, Shadcn/UI, and Vite. (thoughtfully crafted, not vibe coded)
Show HN: Control Claude permissions using a cloud-based decision table UI
Show HN: Control Claude permissions using a cloud-based decision table UI We’ve been building visual rule engines (clear interfaces + API endpoints that help map input data to a large number of outcomes) for a while and had the fun idea lately to see what happens when we use our decision table UI with Claude’s PreToolUse hook.<p>The result is a surprisingly useful policy/gating layer– these tables let your team:<p>- Write multi-factor, exception-friendly policies (e.g. deny rm -rf / when --force; allow cleanup only in node_modules; ask on network calls like curl/wget; block kubectl delete or SQL DROP, each with a clear reason)<p>- Roll out policy changes instantly (mid-run, flip a risky operation from allow → ask; the next attempt across devs and agents is gated immediately– no git pull, agent restart, or coordination)<p>- Adopt lightweight governance that is somewhat agent agnostic and survives churn (MCP/skills/etc)- just add columns/rules as new tools and metadata show up<p>- Get a quick central utility to understand which tools are being used, which tools get blocked most often, and why
Show HN: Claude Code Scheduler
Show HN: Claude Code Scheduler I found myself frequently wanting to schedule tasks in Claude Code (both one-time and recurring) so I built a CC plugin to help with that.<p>To install: /plugin marketplace add jshchnz/claude-code-scheduler /plugin install scheduler@claude-code-scheduler<p>Then just tell Claude what you want (some examples):<p>Every Wednesday at 3am find dead code: unused functions, unreachable branches, commented-out code, and unused imports. List by file with line numbers.<p>Schedule a code review every weekday at 9am. Review commits from the last 24 hours, check for bugs, security issues, error handling gaps, and code that needs comments. Summarize with file:line references.
Show HN: Webctl – Browser automation for agents based on CLI instead of MCP
Show HN: Webctl – Browser automation for agents based on CLI instead of MCP
No other tools from this source yet.