Plans & Billing Models
See the credit allocation for each plan, and the two ways to pay for credits — self-serve through Stripe or metered through a cloud marketplace.
bizSupply ships a single credit unit across every tier. How many credits you get each month is set by your plan; how you pay for them is set by your billing model.
Subscription Plans
bizSupply offers four tiers. Credit allocations and features below live in a configuration the platform can update without a release, so this table reflects the current published catalog.
| Plan | Monthly credits | Price (EUR / month) | Best for |
|---|---|---|---|
| Free | 500 | €0 | Trying the platform, small pilots |
| Starter | 5,000 | €49 | Small teams, light automations |
| Professional | 25,000 | €499 | Growing businesses, production workloads |
| Enterprise | Unlimited | Custom | Large organizations, dedicated support, private deployments |
Each tier also unlocks platform capabilities. The highlights:
- Free — webhook-based events, custom transformers, plugin marketplace.
- Starter — portal support, advanced reports and alerts, rollover credits, user roles, vendor dependency insights.
- Professional — external benchmarking insights, priority support, SSO, feature priority in the product backlog.
- Enterprise — dedicated Customer Success Manager, call scheduling with the product team, custom integrations, private cloud.
For the authoritative, always-current list of features and prices, consult the pricing page. The docs describe the structure of the plans; the pricing page is the source of truth for current numbers.
Billing Models
bizSupply supports two ways to pay for credits. Both use the same credit unit and the same metering pipeline — only the settlement partner differs.
Self-serve (Stripe)
- You subscribe via the bizSupply customer portal.
- Stripe handles recurring payments and invoices.
- On every successful invoice or plan change, your account is allocated the corresponding credit bundle.
- Credits fund your usage until the next renewal.
Self-serve is the default path. Credit cards, direct debit, and a normal Stripe receipt — nothing cloud-specific.
Cloud Marketplace (metered)
- You subscribe through a supported cloud marketplace (for example, Google Cloud Marketplace).
- Your consumption is reported directly to the marketplace on a recurring schedule.
- You are billed by your cloud provider, on the same invoice as your other cloud services.
- No credit cards or separate accounts required.
Marketplace billing is metered: there is no fixed monthly credit bundle to consume. Every credit you use is reported and billed. See Compliance & audit for how usage is reported.
What Counts as Consumption
Every AI call the platform makes on your behalf — classification, extraction, benchmarking, prompt evaluation, chat-style queries, and anything that touches a language model — consumes credits. Exactly how many depends on the model selected, the size of the prompt, and the size of the response.
| Trigger | Consumes credits? | Notes |
|---|---|---|
| Successful AI call | Yes | Charged once, based on reported token counts. |
| Failed AI call (provider error) | No | No tokens returned, no credits consumed. |
| Internal retry after transient failure | No | Only the final successful call is counted. |
| Webhook delivery | No | Webhooks are not AI calls. |
| Job metadata read / balance query | No | Observability endpoints are free. |
What Happens When You Run Out
The platform can either stop new jobs or continue running with a small configurable tolerance, depending on how your account is set up. Either way, you will be notified well before you hit zero.
- Stop on zero — the default. Jobs that would exceed the remaining balance are queued or rejected with a clear quota error.
- Soft tolerance — optional. A small grace band keeps critical jobs running while alerts notify you to top up or upgrade.
- Top-up — one-time credit grants are supported on every plan. Top-ups land as a normal allocation on your ledger, fully auditable.
- Plan change — upgrading mid-cycle grants the new plan’s allocation immediately; downgrading takes effect at the next cycle.
Enterprise accounts carry an unlimited flag on the balance. The ledger still records every consumption event, but the quota layer does not block. "Unlimited" is operational, not semantic — usage is still fully audited.
Related Pages
- RPT overview — the mental model behind credits.
- Fairness & observability — how to see where your credits went.
- Managing your subscription — tactical steps to upgrade, downgrade, and manage payment methods.