Buying Guide

Cloud Credits Explained: What They Cover and What They Do Not

A credit balance is a spending allowance, not a capability. The distinction decides whether an environment is useful or merely well funded.

Cloud Credits Explained: What They Cover and What They Do Not — RunCloudMarket cloud infrastructure guide illustration

Credit balances are one of the most visible things about a cloud environment and one of the most widely misunderstood.

A credit is a spending allowance. It offsets charges. It does not raise limits, unlock restricted services, open restricted ports or change what an account is permitted to do.

An environment with a large balance and a low instance ceiling will hit the ceiling long before the money runs out.

Where credits come from

Source Typical scope Typical life
Free trial Broad, with platform restrictions Fixed window, often 30–90 days
Startup or accelerator programme Broad, sometimes service-restricted 12–24 months
Education or research grant Often service-restricted Fixed term
Commitment or migration incentive Negotiated Contract term
Support or service-level compensation Applied to the account Until spent

Trial credit is the most common and the most restrictive, because it arrives attached to a set of platform limitations.

The three questions

Whenever an environment is described by a credit figure, three things determine whether it is useful:

1. What is the remaining balance? Not the headline the programme started with. Credits are consumed; the number that matters is what is left today.

2. When does it expire? Most promotional credit expires on a fixed date and unused balance is simply lost. Credit expiring in three weeks is worth far less than the same figure with a year to run.

3. What is it valid for? Scope restrictions are common and rarely advertised. Frequent exclusions include accelerator SKUs, marketplace and third-party purchases, support plans, committed-use purchases, licence fees, and premium support.

If you intend to run GPU workloads on credit, confirm the credit applies to accelerator SKUs before committing. That specific exclusion catches people regularly.

Trial restrictions are separate from credit

This is the distinction that matters most on the platforms where it applies.

A free-trial account has a credit balance and a set of restrictions: quota ceilings, some services unavailable, and an automatic stop when the trial ends. The restrictions are a property of the account state, not of the balance.

An upgraded or pay-as-you-go account has a live billing relationship. It may still carry credit, but the restrictions are gone and nothing stops at a deadline.

The platforms where this matters most:

  • Google Cloud — trial versus upgraded billing, with quota and service differences. A Google Cloud account listing distinguishes these explicitly.
  • Oracle Cloud — trial reverts to Always Free resources at expiry; an upgraded tenancy does not. An Oracle Cloud account states which state applies.
  • Azure — a free-trial subscription applies a spending cap that stops deployments; pay-as-you-go does not. An Azure account listing states the offer type.

On each, two environments with identical balances can have completely different futures.

Credits and limits are different systems

To be explicit, because it is the most common misunderstanding:

Credit does Credit does not
Offset charges up to its balance Raise vCPU or instance quota
Reduce the invoice Open outbound port 25
Fund experimentation Grant access to restricted services
Cover overruns during evaluation Accelerate limit-increase approvals

Limits are governed by account state, history and explicit requests. They are a separate axis entirely, and it is the one that usually determines what you can actually deploy. The evaluation guide covers how to check both.

Using credit sensibly

Credit is genuinely valuable for the right things:

  • Evaluation. Running a real workload against a platform before committing is exactly what trial credit is for.
  • Short-lived projects. A migration, a proof of concept, a fixed-term research project.
  • Absorbing early-stage variance while you learn what the workload actually costs.

It is a poor foundation for anything you intend to run indefinitely, because expiry is a cost cliff rather than a slope. A service funded entirely by credit becomes a service with an unbudgeted cost on a known date.

The disciplined approach: measure your actual run rate while on credit, so that when it expires you already know the number. Teams that do this transition smoothly; teams that do not get a surprise invoice.

Frequently asked questions

Can credits be transferred between accounts? Generally no. Credits attach to the billing account that received them.

Do credits cover egress? Usually yes, since egress is an ordinary charge. Confirm against the specific programme terms.

What happens when credit runs out mid-month? On a pay-as-you-go account, ordinary charges resume against the payment method on file. On a trial with a spending cap, deployments stop instead.

Is a large credit balance a good reason to choose a platform? It is a good reason to evaluate one. It is a poor reason to commit to one, because the platform decision outlives the credit by years.

The billing models guide covers how charges accrue once credit is no longer covering them.

Keep reading

Related guides

Talk to us first

Questions about a specific configuration?

Send us the workload profile — vCPU, memory, region, open ports — and we will confirm which listings actually support it before you buy.

Telegram