Plans and limits
What each plan includes, and what counts against it.
Four plans. What separates them is partly volume and mostly capability: history starts at Basic, and crawling, scheduling, uptime, the API and team seats start at Pro.
What each plan includes
| Free | Basic $19/mo | Pro $39/mo | Agency $99/mo | |
|---|---|---|---|---|
| Reports | 3 a day | 300 a month | 1,500 a month | 6,000 a month |
| History and comparisons | No | Yes | Yes | Yes |
| PDF and CSV export | No | Yes | Yes | Yes |
| Site crawl | No | No | 100 pages, 10 crawls | 500 pages, 30 crawls |
| Scheduling | No | No | Yes | Yes |
| Uptime monitoring | No | No | 3 sites | 10 sites |
| API | No | No | 1,000 calls, 3 keys | 4,000 calls, 10 keys |
| Workspaces | 1 | 1 | 3 | 10 |
| Team seats | None | None | 3 included | 10 included |
| White-label exports | No | No | Yes | Yes |
Capabilities by plan
| Capability | From | Why it is worth it |
|---|---|---|
| History | Basic | Turns a report into a trend. Without it you know a page scores 78; with it you know whether last week's change helped. |
| PDF export | Basic | The format for sending an audit to somebody who is not going to sign in. |
| Site crawl | Pro | Finds the problems that repeat across a template, which are the cheapest to fix and the easiest to miss one page at a time. |
| Scheduling | Pro | A regression becomes something you are told about rather than something you find. |
| Uptime | Pro | The one failure that makes every other number irrelevant. |
| API | Pro | Analysis in your deploy pipeline, and reporting in your own tools. |
| White label | Pro | Client-facing work that looks like yours. |
| Workspaces and seats | Pro | Client separation, and access somebody can be given without seeing everything else. |
What counts as a report
| Action | Counts as |
|---|---|
| Analysing a URL from the dashboard | One report |
| Refreshing a tracked page | One report |
| A scheduled run | One report |
POST /reports over the API | One report, and one API call |
| A crawl of 80 pages | 80 reports, and one crawl against the crawl allowance |
| Re-opening a report you already have | Nothing |
| Exporting a report to PDF or CSV | Nothing |
| An uptime check | Nothing |
Crawls are the one to watch. A 500 page crawl is 500 reports, so two of them is a sixth of the Agency allowance. Crawl broadly once to find the template-level problems, then track the pages that matter and let the crawl allowance sit idle until the site changes shape.
When allowances reset
Monthly allowances reset on the first of the month, not on your billing date. Upgrading mid-month gives you the new allowance straight away rather than at your next renewal, and what you have already used is not carried over.
Running out
When the monthly limit is reached, analyses stop until the first of the month or until you upgrade. Nothing is lost: tracked pages stay tracked, history stays intact, schedules pause and resume on their own. You are warned as you approach the limit rather than only when you hit it.
Over the API, GET /account/usage returns what you have used and what remains, so a job can check before it starts rather than failing halfway through. See Account.
Choosing
| If you | Take |
|---|---|
| Look after one site and want to know when it breaks | Basic, and track your important pages. |
| Want the whole site audited, or want this in CI | Pro. Crawl and API are both there. |
| Do this for clients | Agency, for the workspaces and the branding as much as the volume. |
| Are not sure yet | Free. Three a day is enough to see whether the findings are useful to you. |