The current PageLens AI offer starts free, with a one-time launch option and recurring protection for apps that keep changing:
- Free initial check — score, category counts, up to three issue summaries and one complete example fix; no signup or card
- Launch Pass — $29 one time for up to 15 public pages, desktop and mobile evidence, PDF and Markdown exports, agent-ready fixes and one verification re-scan
- Release Guard — $39/month for continuous release QA on one live app
- Studio — $99/month for release QA across a growing app portfolio
The checkout shows the report name, price and scope before payment.
Existing customer plans
Some existing customers retain legacy Watch, Builder, Pro or Agency entitlements. PageLens continues to honour those entitlements inside the signed-in product, but they are not offered as the current public purchase path. Existing customers can review their access and billing state in Settings -> Billing.
If an existing entitlement covers a scan, the form identifies that before submission instead of asking the customer to pay again.
One-time report payments
Launch Pass is a single purchase tied to the submitted app and report scope. It does not create recurring billing, credits or a contract.
The URL and selected report are carried through sign-in to checkout so you do not need to start again after creating an account.
Verification re-scan
The Launch Pass includes one verification re-scan. Use it after deploying the recommended fixes to check whether the captured evidence and findings changed. A verification re-scan is part of that report purchase; it is not a subscription.
Refund requests
Refund eligibility is set out in the Terms of Service. Contact support with the report details so we can review your request against that policy.
Open a support ticket and choose Billing if:
- you paid for a scan that failed before producing a useful report
- you were charged unexpectedly
- you need an invoice or payment clarification
- you selected the wrong option and have not used the report
Attach the scan when the request is tied to a specific run.
Failed scans
Some failures are caused by unreachable sites, blocking, login issues, or invalid route configuration. A failed purchased report can be retried without paying again. If a retry still cannot produce a useful report, support can inspect the scan metadata and advise whether a configuration change or refund is appropriate.