Prove one public journey with 5 sessions, 1 project, limited evidence, and 7-day retention.
StartPricing
Pricing that follows the journeys you need watched.
Start by proving one public path, then scale into monitored signup, onboarding, checkout, and upgrade journeys. Each monitored journey consumes browser session units based on personas and reruns.
Pricing
Choose how many product journeys need coverage.
Plans are sold around journey coverage. Session units stay visible so teams can forecast personas, scheduled runs, and verification reruns.
Capacity example
8 personas x checkout journey = 24 browser session units
Monitor one public journey with 50 sessions/month, 1 project, 3 seats, and manual runs.
Choose StarterCover core authenticated journeys with 250 sessions/month, test accounts, scheduled runs, dedupe, agent prompts, and Card QA.
Start Team trialRun preview and CI regression coverage with 1,000 sessions/month, custom personas, comparisons, and CLI handoff.
Choose GrowthPrivate runners, custom sessions, SSO, audit logs, redaction, retention, and onboarding.
Start Enterprise setupUsage model
Journey coverage is the plan. Session units are the capacity meter.
How do session units work?
One persona, one mission, up to 10 minutes, up to 20 browser actions, capped screenshots, and bounded retries.
Is Card QA metered separately?
No. Card QA, dedupe, agent prompts, and verification context are bundled into the plans. Verification reruns consume normal session units.
Do you edit our code?
No. UserProof discovers, packages, and verifies user-facing problems. Your team or coding agent handles the fix.
Can we test authenticated flows?
Team and higher plans support explicit test-account notes and configured allowed hosts for safe authenticated journeys.
Start small