BCC is one prepaid credit for six categories of usage.
BECCA Cloud Credit (BCC) replaces line-item cloud billing with a single prepaid balance. It is a prepaid service credit for BECCA infrastructure — not a cryptocurrency, not a tradable token, and not usable outside the platform. Rather than reconciling separate invoices for compute, storage and support, your organization draws down one number.
Each package allocates a fixed amount of BCC for its billing period. As sessions run, BCC is drawn from your balance according to what the workload actually used — a heavier inference job draws differently than a storage-only task.
BCC never expires mid-period and does not roll over automatically between periods unless your package specifies otherwise. Balances, draw-downs and renewal timing are reflected in the client portal once live metering is enabled by the provider.
ROI comes from seeing what a workload actually cost.
Because BCC is drawn per session rather than billed after the fact, teams can compare a workload's BCC cost against the value it produced — before committing to a larger capacity package.
An effective rate for any workload is its BCC draw divided by the package's BCC-per-period allowance, multiplied against the period price. Teams typically use this to decide whether to stay on a package or move up a tier.
The worked example to the right uses a simulated workload profile — a 32-core rendering job run four hours a day — to show the shape of the calculation. It is not connected to live metering.
monthly_hours × effective_rate = projected monthly spend
Usage flow: planning to measured result.
Plan
Package selection reserves a BCC allowance for the period.
Connect
A certified node is attached to your organization.
Approve
A named approver clears the workload for execution.
Run
The session executes in a credit-metered state.
Measure
BCC drawn is posted to the ledger as a measured result.