Introduction

deploydiff monitors your web pages and automatically detects visual and content changes between deployments. No manual screenshots, no missed regressions.

What is deploydiff?

deploydiff runs a headless browser against your pages — on a recurring schedule you set, or on demand — captures snapshots, and generates a diff. Your team sees exactly what changed — nothing more, nothing less.

Ready to get started? Follow the Quick Start guide to set up your first project in a few minutes.

Key concepts

Organizations

The top-level container. All projects, members, and billing belong to an organization.

Projects

A project maps to a single web application. It holds all its environments, pages, and batch history.

Environments

Each project can have multiple environments — production, staging, previews. Capture batches are always scoped to one environment but diff batches can operate accross environments depending on the needs.

Pages

A page is a URL path within a project. Pages are defined once at the project level and picked up across all environments.

Domain validation

Before capturing an environment, deploydiff checks that your organization controls its domain, through a verification file you publish there.

Capture batches

A capture batch is a screenshot run for one environment. It visits every enabled page using a headless browser and captures a full-page screenshot of each.

Diff batches

A diff batch compares two capture batches to detect visual regressions. One batch is the reference (baseline env, or previous deployment) and the other is the candidate (e.g. a new deployment).

Notifications

Notifications are created automatically when a batch ends in a non-success state. They track status through an Open → Escalated / Archived lifecycle and include an audit trail of who acted and when.