Environments

An environment represents a deployment target for a project — typically production, staging, or a preview URL. Capture and diff batches are always scoped to a single environment.

Creating an environment

Click New environment inside a project. You need to provide:

• Name — a label for this environment (e.g. "Production", "Staging").
• Base URL — the root URL of the deployment, scheme and domain only (e.g. https://staging.myapp.com). deploydiff combines this with each page path to form the full URL visited during a capture batch.

Settings

The Settings page for an environment has five sections:

General

Rename the environment or change its base URL.

Visibility

Pin the environment to make it appear at the top of the project overview.

HTTP Headers

Add custom HTTP headers that deploydiff sends with every request to this environment — for example an Authorization header to access a staging environment behind a login wall or firewall bypass. Each header can optionally be restricted to the environment's own origin (default) or forwarded to third-party requests as well. HTTP Headers are only visible to organization Owners and Admins; project Members and Participants cannot see them.

Verdict config

Controls what verdict to assign for each of the following situations:

The batch verdict is the worst across all tasks: Fail > Warn > Pass > Skipped.

How much a page may change before it Fails is not configured here: those thresholds are content-driven, so they live in the project's diff config and can be overridden per page.

Notifications

Choose which batch outcomes create a notification for this environment. Capture batch and diff batch notifications can be toggled independently, and both are enabled by default. See Notifications for the full list of outcomes that trigger a notification.

Automation

The Automation page lets you configure two optional recurring behaviours:

Automated captures

Set a recurring schedule for this environment. When the interval elapses, deploydiff automatically launches a capture batch. Available intervals range from every 15 minutes to once every two weeks (your plan may enforce a minimum interval). The last automated capture time is shown on this page.

Automated diffing

After each successful capture batch in this environment you can automatically launch a diff batch:

• Diff vs previous batch — compares the new capture against the previous completed batch in the same environment.
• Diff vs reference environment — compares the new capture against the latest completed batch from another environment in the same project (useful for comparing staging against production).

Both options can be active at the same time.

Pages in an environment

Adding a page to a project does not automatically enable it in every environment. From the environment's Pages tab you can toggle each page on or off. Only enabled pages are included in capture batch runs.

An archived page is listed with an Archived tag and cannot be enabled: it is disabled in every environment for as long as it stays archived.

Your plan sets how many pages can be enabled in one environment; once that number is reached, disable a page to enable another. If an environment has more pages enabled than its plan captures (after a downgrade, for example), nothing is disabled for you: the oldest pages are captured, the same ones in every environment that has them enabled, the Pages tab marks the others, and each capture batch says how many it left out. Disable pages to choose which ones are captured, or upgrade to capture them all again.