Credits, pay-as-you-go and trials: how configurations differ
Look down any platform page in the catalogue and the price spread is striking. Azure configurations run from the low tens of dollars to five figures; AWS does the same. The platform is identical in every case. What differs is the configuration, and configuration names are compressed enough that it is worth unpacking what they describe.
Promotional and prepaid credits
A credit account includes a promotional or prepaid balance that offsets early usage. Credits are a temporary financial buffer, useful for experimentation and proof-of-concept work; they do not change the underlying subscription model or unlock features. A larger credit balance is the main reason one configuration costs more than another on the same platform.
Credits also expire and carry their own terms, which are set by the provider rather than by the marketplace. Where a configuration includes credits, the amount appears in the configuration name before purchase, so you can see exactly what you are buying.
Pay-as-you-go
A pay-as-you-go account follows the standard consumption model: you pay for the resources you use, with no long-term commitment and no bundled balance. These configurations are the least expensive to buy because they carry no credit, and they suit both short projects and ongoing production work. The flexibility is the point.
Free trials
Trial configurations correspond to the provider’s own trial programme, including whatever balance that programme grants. They are the cheapest way onto a platform and the most constrained: trial terms, duration and limits are the provider’s, and they are designed for evaluation rather than production.
Raised service limits
Some configurations are priced by capability rather than balance. An account with outbound port 25 open, a higher droplet or server limit, more vCPU headroom, or raised request-per-minute limits on an AI service is worth more precisely because new accounts do not get those limits by default and raising them usually means a support request and a waiting period.
These are the configurations to look at when a verification delay is not your problem but a service limit is. The comparison page shows how many configurations each platform carries, which is a reasonable proxy for how much variety there is to choose from.
Reading a configuration name
Configuration names are terse but consistent. They generally state the platform, then the distinguishing attribute: a credit amount, a billing model, a limit that has been raised, or a capability that has been enabled. If two configurations differ only in price, the name will say why.
One AWS configuration is quoted individually rather than listed at a fixed price, because what is available varies. It appears in the list with its price shown as quoted on request rather than as a number, and it cannot be added to the cart until the price is confirmed.
Which to buy
Work backwards from the project. If you are evaluating a platform, a trial or a small pay-as-you-go account is enough. If you are starting development with a known runway, credits buy you room to experiment without an immediate invoice. If a specific service limit is blocking you, buy for that limit rather than for balance. And if the workload is already defined and steady, pay-as-you-go plus the provider’s own reserved pricing will usually cost less over time than buying a large credit balance up front.
Whatever you choose, the price shown on the platform page is the price at checkout. Nothing is added afterwards.