Three different things routinely get called free, and they behave nothing alike. Confusing them is how a prototype that cost nothing for three months turns into a running charge nobody budgeted for.
The three kinds of free
Trial credit
A fixed amount of money, usable across most services, that expires on a date. Google Cloud’s prepaid trial credit and Oracle Cloud’s trial credit work this way. Two things end it: spending it, or reaching the expiry date with credit unused. The expiry is the part people forget, because it means an unhurried project can lose the credit without ever having used it.
Credit is broad. That is its advantage over a free tier, because it lets you evaluate expensive services. It is also why it drains faster than expected.
Always-free allowances
A perpetual allowance of specific resources, at specific sizes, that does not expire. Oracle Cloud’s Always Free tier is the most substantial example among the platforms in this catalogue, and it is genuinely useful for small persistent workloads rather than only for evaluation.
The constraint is shape rather than time. You get particular instance types in particular regions at particular sizes. Build within the shape and it keeps working; step outside it and you are simply billing normally.
Introductory free tiers
An allowance that applies for a fixed period from account creation, typically twelve months, after which the same usage bills at standard rates. A good deal of what gets called a free tier is this. The resources keep running, the allowance stops, and the change is invisible from inside the application.
This is the category that produces the classic surprise: an instance launched during month one, still running in month thirteen, now chargeable.
What free tiers tend not to include
Across platforms the exclusions are more consistent than the inclusions.
- Data egress beyond a small allowance. Often the first thing a real workload exceeds.
- Managed service baselines. Load balancers, NAT gateways and Kubernetes control planes commonly sit outside free allowances even when compute does not.
- Premium support. Free accounts generally get documentation and community support only.
- GPU and accelerated compute. Almost never included, and usually quota-restricted on new accounts regardless.
- Snapshots and backups beyond a small quota.
- Specific regions. Allowances are frequently restricted to a subset of regions, which may not be the one nearest your users.
Reading the terms that matter
Four questions settle most of it.
- Is the limit time-based, amount-based or shape-based? This determines how it ends and therefore what you should watch.
- What happens at the boundary? Does usage bill normally, or does the service stop? Both models exist, and the difference matters enormously for anything in production.
- Which regions and sizes qualify? An allowance in a region far from your users is a latency decision disguised as a cost decision.
- Is a payment method required, and what is it for? Most platforms require one for verification and will charge it once the allowance ends.
These terms are set by each provider and change without notice, so check the provider’s own current documentation before you design around an allowance.
Build so the boundary is survivable
The useful discipline is to assume the free period ends while the workload is still running, because it usually does.
- Set billing alerts on day one, while everything is still covered. You want the thresholds proven before they are needed.
- Record the expiry date somewhere you will see it, not in the account you are evaluating.
- Know the post-allowance price of everything you launch. If the answer is uncomfortable, that is information worth having in week one rather than month thirteen.
- Keep evaluation separate from anything that matters. A trial account is a fine place to learn a platform and a poor place to host something people depend on, because the account’s status changes on a date rather than on your schedule.
- Expect quota limits regardless. New accounts carry low service limits whether or not an allowance is attached, so a free tier does not mean generous capacity.
Where the catalogue fits
Several configurations available here include platform credit, and the credit amount is stated in the configuration name so you know what you are buying before you buy it. What credit cannot do is change the provider’s own rules about it. The amount, the expiry and the eligibility conditions are the provider’s, not the marketplace’s, and they apply the same way they would to an account you created yourself.
Which means the honest framing is this: credit buys you runway to evaluate or to build without immediate cost. It does not buy you an exemption from understanding what things cost once the runway ends. Teams that treat it as the former get a lot of value from it. Teams that treat it as the latter get a surprise.