Plans & credits
Two separate things govern a Cloud account: credits, which are consumed per run, and a plan, which sets the limits your organization operates under. Buying credits does not change your plan, and upgrading your plan does not remove the need for credits — it grants them.
Both belong to the organization, not to individual members.
Credits
Section titled “Credits”Every node declares what it costs to run. Starting a workflow charges the sum of its enabled nodes up front, before the first node executes: if the balance does not cover it, the run is rejected with 403 insufficient credits and nothing is executed or partially charged. Disabling a node on the canvas takes it out of the total.
The per-node cost is listed in the node reference.
Credits are also charged per call when a node is invoked as an MCP tool, so a chat client working through your BlockNext server draws on the same balance.
The ledger
Section titled “The ledger”A balance is not a counter that goes up and down — it is the sum of an append-only ledger. Every grant is a positive entry, every charge a negative one, each carrying a reason and the run it belongs to, and the full history is visible in the app.
Grants can expire. Monthly plan credits carry an expiry a month out; welcome credits and credits you buy do not expire. Your balance is the sum of the entries that have not expired, which is why it can fall without you running anything: a month-old grant simply stopped counting.
Buying more
Section titled “Buying more”Credit packs are bought outright, at a fixed unit price with a minimum and maximum per purchase, and they never expire. This is independent of your subscription — a free-plan account can buy credits, and buying them does not start one.
Plans are free, basic, pro and ultra, each billed monthly or yearly. Beyond price, a plan sets:
| Limit | Controls |
|---|---|
| Welcome credits | A one-off grant when the subscription starts; does not expire |
| Monthly credits | Granted at the start of each billing period; expires after a month |
| Concurrent runs | How many of your organization’s runs execute at once — the rest queue |
| Workflows | How many workflows you can keep |
| Organization members | How many people can join |
| Scheduled triggers | Whether a schedule can fire at a specific time of day |
| Marketplace selling | Whether you can publish workflows for sale |
| Early access | Whether new features reach you before general release |
Current values and prices are on the pricing page in the app — this page describes what each limit means, not what it is set to today.
The concurrency limit is worth understanding, because it is the one you feel under load rather than at a boundary: runs above it are not rejected, they wait. A burst of triggers on a low-concurrency plan completes, just not at once.
Subscription lifecycle
Section titled “Subscription lifecycle”A subscription starts once payment completes and moves through pending → active, with past_due if a renewal fails, cancelled when you cancel, and expired at the end of the period. An organization has at most one active subscription.
- Cancelling takes effect at the end of the paid period, not immediately — you keep the plan until then, and you can undo a pending cancellation before it lands.
- Renewal extends the period automatically while auto-renew is on, and grants that period’s credits.
- Credits already granted are yours; they are not clawed back when a plan ends or changes.
Invoices and payment
Section titled “Invoices and payment”Every completed payment — subscription, credit pack or marketplace purchase — writes an invoice you can list in the app. Card details are never held by BlockNext: payment runs through the provider’s hosted checkout, and the billing portal link in the app opens the provider’s own page for payment methods and receipts.
Checkout sessions expire after 30 minutes; an abandoned one costs nothing and can simply be started again.