Consumption credits are a currency that a software vendor defines, sells in advance and then deducts as the customer uses its services. Instead of buying a fixed number of users, cores or hosts, the customer buys a balance of credits, and each service draws on that balance at a rate the vendor publishes. Sumo Logic’s definition is typical: a Credit is “a pre-paid unit of value” that is consumed by use of the SaaS Services at the applicable Credit Burn Rates.[4] Trend Micro calls its Credits “the universal licensing unit” for products on the Trend Vision One platform.[7]
A related model, the prepaid unit pool, also uses a vendor currency but does not use it up. Altair customers buy a pool of shareable Altair Units; users draw units from the pool to run products and the units “return to the pool after use”.[12] This article compares both families. The wider subscription and consumption model, including Autodesk Flex tokens and enterprise commitments, is in Subscription and consumption licensing.
Scope and definitions
Credit schemes share a vocabulary even when the names differ:
- Unit of value. The credit itself. Snowflake bills compute “using purchasable credits”, which it calls Platform Credits, and bills AI features in a separate unit, AI Credits.[1]
- Burn rate or multiplier. How many credits one unit of use costs. Sumo Logic defines the Credit Burn Rate as “the number of Credits required to complete a Product Variable specific UOM”, set in the customer’s Order Form.[4] Salesforce says customers consume Flex Credits “at the applicable multiplier rate based on the Usage Type”.[9]
- Price per credit. What the customer pays for each credit. For Snowflake, the billed cost of compute is the number of credits consumed multiplied by the price of a credit.[3]
- Credit period. The time within which the balance must be used. Trend Vision One Credits “expire at the end of the Subscription Period”.[7]
Separating the burn rate from the price matters. A vendor can change what a service costs by changing either one, and the two are often set in different documents.
How it works
Buying a balance
Credits are bought up front, either as a count of credits or as a currency amount. Snowflake offers two purchase models: On Demand, “where usage is invoiced in arrears every month”, or Capacity, “where a set dollar amount of usage is purchased up front”.[1] Capacity pricing applies the Platform Credit Discount in the Order Form to the On Demand credit price, and purchased Capacity “may be applied toward any of your Accounts”.[1] Oracle sells Annual Universal Credits as a Total Credit Value for the services period, decremented monthly to reflect actual usage of each activated IaaS and PaaS service.[10]
Some credits come bundled with another purchase. Salesforce states that “a quantity of Flex Credits is included with certain Salesforce Services”, with the entitlement shown in the Usage Details table of the Order Form.[9]
Drawing the balance down
Each vendor publishes how use converts into credits. Snowflake’s virtual warehouses use Platform Credits at rates based on their size while running; when a warehouse starts or resumes, “a minimum of one minute’s worth of Platform Credits will be consumed”.[1] Serverless features are measured in Compute-Hours, one of which is “the computing resources comparable to running an XS Virtual Warehouse for one hour”, billed at one Platform Credit per Compute-Hour times a feature multiplier.[1]
Salesforce publishes a multiplier for each usage type, with lower multipliers in sandboxes. A standard Agentforce action costs 20 Flex Credits in production and 16 in a sandbox.[9] Sumo Logic charges for log ingest by data tier, and its Infrequent Tier “has a pay-per-search pricing model, and very low ingestion cost”.[6] Sumo Logic also describes a credit as a unit of measure that tracks use, “whether data ingested (GB), storage, or metrics, throughout a contract period”.[5]
Region and edition uplifts
The same activity can cost a different number of credits, or a different price per credit, depending on where and how it runs. Sumo Logic credits “may be subject to uplifted Credit Burn Rate(s)” based on the deployment region, and the European Sovereign Cloud is licensed as a separate deployment with an uplift.[4] Snowflake prices its On Demand Platform Credit by cloud provider, region and edition.[1]
Expiry, rollover and forfeiture
Unused credits usually expire. Oracle states that an Annual Universal Credit amount “must be used within its applicable yearly Credit Period”, and that pre-paid unused amounts “are non-refundable and are forfeited” at the end of it. Monthly Universal Credits expire at the end of each month.[10] Salesforce Flex Credits must be used before the Order End Date, “and no rollover will be permitted”.[9]
Rollover exists where the order grants it. Snowflake’s consumption table refers to “eligible Capacity Rollover” from a prior Order Form being added to the balance of a renewal Order Form, and its documentation reports a rollover balance calculated at the end of a contract term as the contract amount less usage in currency.[1][2]
Running out
Vendors handle an exhausted balance in three ways:
| Vendor | What happens when the balance is used up | Source |
|---|---|---|
| Oracle | Excess usage in a month is invoiced at the Overage Unit Net Price in the rate card | [10] |
| Snowflake | Usage is billed at On Demand prices once all free usage and capacity balances are exhausted | [2] |
| Trend Micro | Use continues uninterrupted, the balance shows as negative, and the vendor contacts the customer to renew or buy credits | [8] |
Returnable unit pools
Altair Units work differently. The Altair help states that each Altair Unit purchased gives 1,000 license features in the licence file, and that units-based applications draw those features.[11] Units return to the pool after use, and users can run several applications at once on a machine while “only drawing units for the most valuable product”.[12] The pool is therefore a cap on concurrent use, closer to concurrent licensing than to a credit balance that is spent. The draw values for each product are covered in Altair Units and unit draw.
Vendor comparison
| Vendor | Unit | Bought as | Drawn by | Expiry or rollover |
|---|---|---|---|---|
| Snowflake | Platform Credits, AI Credits | On Demand, or Capacity in dollars | Warehouse size and running time; Compute-Hours times multiplier | Eligible Capacity Rollover into a renewal order[1] |
| Sumo Logic | Credits | Prepaid for a contract period | Credit Burn Rate per unit of measure, by data tier and region | Tracked against a contract period[5] |
| Trend Micro | Credits | Purchased upfront | Automatically by enabled solutions and packages | Expire at end of Subscription Period[7] |
| Salesforce | Flex Credits | Included with certain services, per Order Form | Multiplier per usage type, lower in sandboxes | Use before Order End Date, no rollover[9] |
| Oracle | Universal Credits | Annual or Monthly credit amounts | Monthly decrement at service rates | Forfeited at end of credit period[10] |
| Altair | Altair Units | A pool of units | Drawn while an application runs | Returned to the pool after use[12] |
Relationship to other license models
Credits sit on top of ordinary subscription terms rather than replacing them. Trend Micro’s agreement defines the Subscription Period as the limited period “for which Company has the right to use and/or receive Products”, and the credits expire with it.[7] Credits also change what an effective license position has to track: not a count of installations against entitlements, but a balance, a burn rate and a date. Snowflake exposes the balance in an organization usage view so that customers can monitor it.[2] Sumo Logic shows credit usage and contract periods on the Account Overview page.[5]
Reconciliation also changes. With credits there is often no annual true-up; overage is billed monthly instead, as Oracle does at the Overage Unit Net Price.[10]
Criticism and challenges
A credit is only as predictable as its rate card, and vendors reserve the right to change rates. Salesforce states that “usage types, tiers, and associated multipliers may be updated from time to time”.[9] Forfeiture rules mean that buying too much is a sunk cost: Oracle’s unused annual credits are non-refundable.[10] Buying too little can cost more per unit: Snowflake’s Capacity price is the On Demand price less the Platform Credit Discount in the Order Form, and usage after the capacity balance is exhausted is billed at On Demand prices.[1][2] Because each vendor defines its own credit, a credit at one vendor has no fixed relationship to a credit at another.
Out of scope
This article does not cover cloud provider spend commitments sold by hyperscalers, marketplace private offers, or user and device subscriptions that have no metered component. Bring-your-own-license conversions into cloud credits are covered in Cloud BYOL and authorized cloud environments.