Cloud credits: how they actually work

Credits are a spending balance, not a free plan

A cloud credit is prepaid money on your account. It offsets usage on the services the programme covers, and it runs down as you use them. Nothing about it makes your architecture free.

Three limits worth reading first

Scope: some programmes cover only compute and storage, and exclude managed databases, support plans or marketplace purchases. Time: credits usually expire on a fixed date, often twelve months out, whether you used them or not. Eligibility: many are for new accounts, early-stage companies or programme members only.

The part that surprises people

When the balance hits zero, the account does not stop — it starts billing the card on file. A workload sized for a generous credit balance can produce an uncomfortable first real invoice. Set a budget alert on day one, not on the day the credits expire.

How to get real value from them

Spend credits on things you would have paid for anyway, keep a note of the expiry date, and avoid designing around a service the credits do not cover. If the programme requires an application, apply before you need the capacity — approvals are rarely instant.

Where to look

The credit listings here show the headline balance, who qualifies, whether a card is required, and the date we last read the provider's terms. Start with the eligibility line; it saves the most time.