Every Wolfix plan includes scans — what changes is how many you get, how often Wolfix can re-scan on a schedule, and which projects you can monitor. This article explains the shape of those limits so you can pick the right plan. For the exact numbers and current pricing, see the pricing page.
What counts as a scan
A scan is a single run of the pipeline against one project — quick or deep, manual or scheduled. Each run counts once toward your allowance.
Manual scans
Every time you press Start scan or Re-scan, that run counts against your plan's allowance.
Scheduled scans
Each automatic run from a recurring schedule counts the same as a manual scan. A weekly schedule uses more of your allowance than a monthly one.
Quick vs. deep
Both modes count as one scan. A quick scan is not cheaper than a deep scan against your allowance — the difference is coverage and duration, not cost.
Per project
Allowances and recurring schedules are tracked per project, so a busy project and a stable one each draw from the same plan-level budget.
What changes across plans
The three plans differ along a few axes. The table shows the shape of those differences — not the figures, which live on the pricing page and change over time.
| Capability | Free | Pro | Business | | --- | --- | --- | --- | | Number of scans | Limited allowance to try Wolfix | Higher allowance for active projects | Highest allowance | | Recurring schedules | Not included | Included | Included | | Projects monitored | Single project | Multiple projects | Most projects | | Scan modes | Quick and deep | Quick and deep | Quick and deep |
Both scan modes are available on every plan — the mode you choose never depends on your tier. What the higher plans add is volume and the recurring-scan monitoring layer.
Exact figures live on the pricing page
Scan counts and limits are set on the pricing page so this article stays correct as plans evolve. Always check /pricing for the current allowance before you plan a monitoring cadence.
How to stay within your allowance
If you are watching your scan count, a few habits keep it under control.
- Match your recurring cadence to your release rhythm. A monthly schedule on a stable project uses far fewer scans than a weekly one, with no real loss of coverage.
- Use quick scans while iterating. They count the same as a deep scan, but they finish faster, so you spend less time waiting when you only need a fast read on document and code gaps.
- Re-scan once a change is actually live. Re-scanning a fix that has not deployed yet wastes a scan — confirm your deploy finished and the page is reachable first.
Upgrade when monitoring pays off
The most common reason to move from Free to a paid plan is recurring scans: the point where you want gaps to surface on their own rather than remembering to re-scan. See /pricing to compare.
When you reach a limit
If you hit your scan allowance, new runs are paused until your allowance resets or you upgrade. Your existing reports stay available — reaching a limit never deletes past results. To keep scanning immediately, upgrade from the pricing page; otherwise your allowance refreshes on your plan's billing cycle.