Billing
How Free, Pro and measured-usage PAYG billing work for Andesyte Code Security.
Plans
| Plan | Usage | Best for |
|---|---|---|
| Free | Fixed safety quotas, no cost | Public open-source repositories |
| Pro | Flat monthly subscription per paid developer, with an included usage allowance and optional capped overage | Private repositories and autofix workflows |
| PAYG | Postpaid delivered AI usage, subject to a customer-set monthly limit | Variable usage for one connected account |
Current prices live on the pricing page and the billing page, not here, so this page doesn't go stale when prices change.
Pro remains a recurring subscription. PAYG has no monthly base fee and uses a Stripe activation-date monthly billing period.
PAYG is available
Set a monthly limit in the billing page, complete Stripe setup and pay only for recorded model input and output tokens. There is no monthly base fee.
Usage rate
The customer rate does not depend on the provider model, and is published on the billing page rather than here. Historical usage keeps the versioned rate that was effective when the work began.
How measured usage works
Before billable AI work starts, the Gateway reserves a hard upper-bound amount using known input and the provider-enforced maximum output. Admission includes:
- settled rated usage in the current Stripe-anchored period;
- every active reservation; and
- the new requested reservation.
After the provider responds, the reservation is settled against actual input and output. A customer is never charged more than the reservation. If provider usage exceeds it, Andesyte absorbs the difference, blocks the contract and raises an incident.
Unknown provider completion stays reserved for investigation. A reservation is released only after an explicit failure before the provider call begins.
Walkthrough, pre-merge and audit outputs are separate actions, even when they belong to one code review. The billing page groups them under that code review without merging their ledger identities. Static scanners, safe-only runs, LLM-disabled actions and undelivered outputs cost $0.
Limits and availability
PAYG requires a customer-set monthly measured-usage limit in whole-dollar increments, within a range shown on the billing page. It does not require prepaid credits or auto-recharge. You can change the limit from the billing page. Pro overage requires explicit consent and its own limit.
When billing enforcement is unavailable, new billable AI calls fail closed. Eligible non-billable scanners (OSV, static analysis and secret detection) continue independently.
Subscription states
- Active or trialling: applicable paid entitlements are available.
- Past due: base Pro access can remain, but PAYG work and Pro overage stop.
- Paused or unpaid: paid entitlements stop immediately.
- Cancelled or incomplete expired: the connected account returns to Free.
- Unknown: billable work fails closed until the state is verified.
Billing page
The billing page shows:
- settled measured usage;
- active reservations;
- the amount remaining before the limit;
- the Stripe-anchored billing period;
- invoice timing and subscription controls; and
- Pro-overage consent when that rollout gate is available.
Stripe hosts payment methods, invoices and subscription management. Each connected account has one canonical Stripe customer and subscription binding; events with mismatched customer or subscription identifiers cannot change another account.
Switching plans
- Free → Pro: use Upgrade to Pro on the billing page.
- Free → PAYG: set a limit and continue to Stripe from the billing page.
- Pro → PAYG: cancel Pro through Manage subscription, then set up PAYG.
- Pro → Free: cancel through the Stripe Billing Portal.
- PAYG → Free: cancel the PAYG subscription through the Stripe Billing Portal.
Historical credit-pack and auto-recharge records remain available for accounting, but those purchase and charge routes are retired and return no new billing side effects.