Monitoring plans
Choose monitoring only after Project Pages, a baseline scan, checkout readiness and confirmed subscription state are clear.
Account owners and finance reviewers
Feature availability
Product, package, provider and deployment boundaries for this page.
- Available from
- Current documentation
- Providers
- paddle
- Deployment modes
- cloud
Product screenshots
Current customer-safe screenshots are generated from the application so examples do not drift from the product.
Before buying monitoring
Monitoring is the recurring check path for a project that already has reviewed Project Pages and a completed baseline scan. Billing can show plan and subscription state, but scheduled monitoring cannot produce useful comparisons until the first scan exists. Use this page when you need to decide whether to buy Plus, use included monitoring from Pro, wait for provider confirmation or return to the project first.
Confirm baseline and scope
Follow the path `Projects → Project detail → Monitoring → Billing`.
- Open /projects and choose the project you want monitored. Result: the project detail page shows Project Pages, latest scan/report state and Monitoring controls.
- Confirm the project has reviewed Project Pages for the public pages you want checked again. Result: recurring scans stay inside the same approved boundary.
- Confirm a baseline scan has completed and produced a report. Result: monitoring can compare future findings against a known starting point.
- Open /billing while switched to the same account. Result: Billing shows the account subscription state, payment provider readiness and monitoring plan cards.
- Read the plan ladder and choose Plus only when checkout is available, or use Pro when it already includes monitoring. Result: the cadence, renewal timing and credit limit match the project before payment.
- If baseline or scope is missing, return to the project and finish that step before checkout. Result: payment does not create a monitoring subscription that cannot run.
Choose Plus
Choose the smallest plan that matches the project cadence and page limit. The Plus checkout route is `/checkout/plus` when Plus is available. Public checkout paths are useful only when the plan is enabled and the project already meets the baseline and scope requirements.
- Basic is enough when a monthly evidence refresh is all the project needs.
- Plus is the first recurring path for weekly checks, alerts and larger scan allowance.
- Pro keeps monitoring on and adds generated remediation tasks, team/client workflow and larger pooled credits.
- Unsupported pages do not become monitorable through payment; review Project Pages before checkout.
- Monitoring compares current findings against the baseline; it does not replace a new full audit when the public journey changes materially.
Wait for subscription readiness
After checkout, return to Billing and wait for provider-confirmed subscription state before expecting scheduled runs. WebRiskOps uses stored provider webhook records, not the browser return page alone, as the source of truth.
- Active allows scheduled checks within the plan cadence and page limits.
- Pending means provider confirmation has not updated product entitlement yet.
- Past due can block new monitoring runs until provider state recovers.
- Cancellation scheduled means access may continue until the current term ends.
- Cancelled means new scheduled monitoring needs another available plan.
Continue to scheduled scans
When Billing is active and the project monitoring setup is saved, open [Scheduled scans](/docs/monitoring-retests/scheduled-scans) to review recurring runs and [Monthly summaries](/docs/monitoring-retests/monthly-summaries) for the monitoring evidence rollup.
- Monitoring plan required means choose Plus or a stronger included plan and wait for subscription readiness.
- Baseline scan required means complete the first scan first.
- Subscription past due means resolve provider state before new scheduled runs continue.
- Project Pages missing means return to the project and review public pages.
- Plan deferred means choose the available plan named in the disabled reason.
Related documentation
Was this page helpful?
Feedback goes into the product documentation review queue.

