Future local-software path for larger audits running on the user's machine instead of hosted public workers.
Future local software
Heavy audits run locally.
The public website should stay lightweight. Larger crawl concepts such as Pro Local, Local Pro+, Extreme, and Enterprise/custom belong to future local software or custom engagements.
Closed access: public signups, live audits, and billing are not available yet.
A future local app should run heavy audits locally. The website/API may later check account or license status only, but no activation system exists yet.
Local software concepts describe operator-controlled execution and local report storage, not public hosted SaaS availability.
Planned local limits
These labels describe a future local-software direction only. They are not public website presets, purchase options, or active license tiers. There is no public hosted Pro tier in the current plan.
Broader local audits for heavier analysis using the operator/user machine and local report storage.
Very large local diagnostics for heavy crawl testing, not hosted public worker execution.
Custom scope, limits, support, VPS/dedicated or contract-specific execution depending on the engagement.
License direction, not implemented
A future local app may call the website/API only for account, entitlement, or license checks. This skeleton does not implement license activation, device binding, accounts, billing, auth, or quota storage.
Why local execution
Moving larger audits to the user's machine protects hosted workers, reduces Cloudflare cost exposure, and keeps heavy crawl CPU, memory, and network usage outside the public website path.