Your team shares a single credit balance. Set a dollar cap per pull request (e.g. @budgetscan $0.50). Credits deduct based on actual scan cost, and failed runs are never charged.
Planned prepaid credit packs: no subscription, no seat fees. Prices and terms are a draft and may change before launch. Scans rarely fail, and a failed scan is never charged.
For independent developers & open-source projects
@budgetscan $X command syntaxOne unified credit balance for the whole engineering team
--max-delayBring your own infrastructure and custom LLM endpoints
Compare estimated pay-per-scan costs with per-seat pricing. The inputs and assumptions here are illustrative.
Illustrative: assumes an average scan costs about 28% of its cap and a seat price of $50 per developer per month. Real per-scan costs will replace this once we have measured them. The seat price is a placeholder, not a quote from any vendor.
Select a PR scenario and test budget caps like @budgetscan $0.50 --max-delay 5m — a conceptual simulation with mock numbers, not a live scan.
How our planned pay-per-scan credit model works.
Instead of paying a recurring monthly fee per developer seat, your team shares a prepaid balance. Each scan deducts only what it actually cost within the cap you set. Full billing terms will be published before launch.
Failures are rare, and if a scan encounters an infrastructure error or unhandled exception, zero credits are deducted. You only pay for completed runs.
Yes. Self-hosted runners can call your own API endpoints (OpenAI, OpenRouter, Google Vertex AI, or local Ollama/vLLM) with 0% compute markup.
When approaching the deadline, the budget governor stops scheduling new work and exports a partial report listing the files covered, preventing pipeline timeouts.