Limits, cooldowns and the queue
How many scans can run at once, how long to wait between manual rescans, and how work is prioritized.
| Limit | Free | Pro | Studio | Agency | Team |
|---|---|---|---|---|---|
| Scans at once, per organization | 1 | 2 | 3 | 5 | 10 |
| Scans at once, per site | 1 | 1 | 1 | 1 | 2 |
| Wait between manual rescans | 60 min | 5 min | 5 min | 5 min | 5 min |
| Manual live-site scan | 5 / month, 1 credit each | Free, unlimited | Free, unlimited | Free, unlimited | Free, unlimited |
Priority
Work is queued by priority rather than by arrival. A pull request check outranks a background advisory review, because somebody is waiting for one and nobody is waiting for the other. Free scans run on the lowest-priority queue.
A scan that cannot start now is queued, not dropped. The site shows the work in progress while it waits.
Questions
Why can I not run two scans on the same site at once?
Two concurrent scans of one application would race on the same facts and baselines, and would look like load to your server. Team plans allow two per site; everyone else runs one at a time.
Can I raise my limits without changing plan?
Credits can be topped up, but concurrency and site limits come with the plan. If you need something between two plans, talk to us.
Something here wrong, missing or out of date? Tell us and we will fix the page.