Open source

Snapvisor is built on a proven open-source visual-diff engine. The core is inspectable and self-hostable; the hosted service adds the review dashboard, integrations, and the MCP server.

An open core

The engine that captures and compares screenshots is open source, and so are the SDKs you install — Snapvisor ships them as @snapvisor packages, open-source (MIT) forks of the @argos-ci SDKs with source at github.com/DevinoSolutions/snapvisor-js. You can read the code, file issues, and run it yourself. The upstream repository is where engine issues live.

Self-hosting

Because the core is open, Snapvisor can be self-hosted. The repository ships a Dockerfile and a production Compose file; you bring Postgres, an S3-compatible bucket, and a proxy. Once it is up, point your @snapvisor SDKs at it the same way you would the hosted service. See Self-hosting for the services, the required environment variables, and the first-run steps.

For open-source projects

Open-source repositories can embed a Snapvisor README badge that links to the project's latest approved reference build, and may qualify for open-source sponsorship. Set the badge up from your project's settings.

Not sure which credential to use when scripting against a self-hosted or hosted instance? See Access tokens.