Production monitoring

Run approved Playwright tests against production on a schedule. Proof does not use AI when the test passes.

One dispatcher, durable sweeps

One Vercel Cron request finds each due schedule and starts a Workflow. The Workflow groups the active tests and sends them to an isolated Playwright worker. The worker runs Chromium, returns results, and does not call AI.

Cron only starts the work

Proof stores schedules in its database. Do not add a Vercel Cron definition for each customer.

Create a monitor

bash

curl "$PROOF_PUBLIC_URL/api/monitors" \
  --request POST \
  --header "Authorization: Bearer $PROOF_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "projectId": "project_storefront",
    "name": "daily production",
    "cadenceMinutes": 1440,
    "maxTests": 50,
    "maxParallelism": 4
  }'

The API key determines which organization owns the monitor. The monitor uses the Project test URL and test settings.

The current Hobby deployment runs daily

The checked-in Cron runs once per day. A Pro deployment can lower PROOF_MONITOR_MIN_CADENCE_MINUTES and change the Cron schedule together. Proof rejects schedules that run faster than the configured minimum.

Retry before escalation

Proof repeats every failure once, including a worker timeout. If the failure repeats, it records logs, screenshots, and paths. It then sends the result to the optional signed alert webhook. Proof does not use AI unless both AI settings are enabled.

Hard spend boundary

Each test reserves two cents before it runs. That covers one worker task and one retry. All billable Proof entry points share a monthly $10 budget. When the budget is used, Proof records the blocked work and does not start compute.

Provider billing is separate

Proof's budget is conservative. It is not a provider invoice meter. The current Vercel Hobby team has no metered overage billing. A future Pro migration must add team Spend Management before activation.