Proof Docs
Open Proof

Cost controls

Proof starts with live work and AI turned off. Enable them separately, set provider limits, then test one Check first.

Safe defaults

Local setup, linting, type checks, unit tests, builds, Workflow checks, CLI builds, and the documentation site do not create Vercel resources or call an AI provider.

dotenv
PROOF_LIVE_EXECUTION_ENABLED=false
PROOF_AI_EXECUTION_ENABLED=false
PROOF_MODEL_TIER=budget
PROOF_ALLOW_PREMIUM_MODELS=false

Independent interlocks

VariablePurposeDefault
PROOF_LIVE_EXECUTION_ENABLEDAllows live Workflows and isolated workspaces.false
PROOF_AI_EXECUTION_ENABLEDAllows any AI SDK or Gateway request.false
PROOF_MODEL_TIERSelects budget or premium model policy.budget
PROOF_ALLOW_PREMIUM_MODELSSecond opt-in required for premium routing.false
PROOF_ALLOW_LIVE_VERIFICATIONAllows billable integration verification scripts.false
PROOF_ALLOW_BILLABLE_SETUPAllows creation of a reusable browser snapshot.false
PROOF_ALLOW_UNCACHED_BROWSER_RUNTIMEAllows a fresh Chromium download instead of a snapshot.false
PROOF_MONITORING_ENABLEDAllows Cron to run saved production tests.false
PROOF_MONITOR_AI_ESCALATION_ENABLEDAllows AI to recheck repeated monitor failures.false
PROOF_MODEL_MAX_RETRIESCaps AI SDK retries for each logical model call; run telemetry records the resulting attempts.0
PROOF_HARD_SPEND_CAP_CENTSMonthly spending limit. Values above 1000 are rejected.1000
PROOF_MONITOR_MIN_CADENCE_MINUTESRejects schedules faster than the provider Cron wake-up.1440

Proof reserves a small amount before each billable action and blocks new work at $10. This is not an invoice meter. It works with provider controls. Vercel Spend Management can pause a Pro team. Hobby teams stop at their included limits.

Run the first test

  1. Use a capped test database and apply reviewed migrations.
  2. Set up one Clerk development organization and one fixture repository.
  3. Set catalog and exploration limits to one.
  4. Enable live execution while AI stays off. Then repeat one saved fixture test.
  5. Review the isolated workspace lifetime, stored files, Workflow steps, and database use.
  6. Enable AI for one budget-tier Check only after you set a provider limit.

Operate with AI paused

Saved tests can still run while AI is disabled. Proof skips discovery and does not build new Checks. It marks failures that need an AI recheck as inconclusive. It does not report them as regressions.

Stop conditions

Turn the settings off at once if a Job loops, a deployment does not become ready, isolated-workspace cleanup fails, usage exceeds the test limit, a provider ignores its limit, or a delivery repeats. Keep the Job record. Check the expected retry cost before you try again.