Oracle Cloud is generous compute shapes and an unusually cheap egress policy. Kamatera is servers sized by the resource rather than chosen from a menu. This page puts the two side by side — the live configurations and prices from our catalogue, then the differences that actually decide the choice.
| In our catalogue | Oracle Cloud | Kamatera |
|---|---|---|
| Product | Buy Oracle Cloud Account | Buy Kamatera Account |
| Configurations in stock | 16 | 2 |
| Lowest price | $40 | $30 |
| Highest price | $90 | $70 |
| Example options | FT $300 / Phoenix / FT $300 / Singapore / Free Trial $300 / Singapore | Kamatera Free Trial / Kamatera Cloud Server |
| View options | View options |
Prices and configuration counts are read from the live catalogue. Specifications are listed exactly as supplied; nothing here is estimated.
Billing model is the real difference
Everything else on this page is secondary to one structural difference: Oracle Cloud meters what you use, and Kamatera charges a published monthly figure. That is not a pricing detail, it is a difference in who carries the uncertainty.
With Oracle Cloud you pay for exactly the compute-seconds, requests and gigabytes you consume, which is honest for elastic workloads and unnerving for fixed ones — the bill is knowable only in arrears. With Kamatera the number is fixed in advance and idle capacity is your problem rather than your accountant’s.
If an unexpected invoice would be a genuine problem rather than an annoyance, that constraint decides this comparison before any feature does.
Where Oracle Cloud is the stronger choice
Price on the axes that usually hurt. Egress allowances are markedly more generous than the other large platforms, and the compute shapes are competitive.
Best suited to: teams that want hyperscaler-shaped infrastructure without hyperscaler-shaped data transfer bills, and anyone running Oracle software.
Regions: A wide and still-expanding region list, with many single-region countries covered for residency reasons.
Worth knowing: Tenancy and compartment concepts differ from the other platforms; budget time for the mental model rather than assuming AWS habits transfer.
Where Kamatera is the stronger choice
Configurability. vCPU, RAM, storage and bandwidth are selected independently, so you pay for the shape you actually need instead of rounding up to the next tier.
Best suited to: workloads that do not fit standard instance shapes — unusual CPU-to-RAM ratios, or capacity that changes often.
Regions: An unusually wide data-centre list for a provider of this size, spanning North America, Europe, Asia and the Middle East.
Worth knowing: Flexibility invites over-provisioning. Size against measurements, not against the maximum you might one day want.
The trade-offs, stated plainly
Oracle Cloud: A smaller ecosystem, fewer third-party integrations, and a much smaller pool of engineers who have used it in anger.
Kamatera: A smaller platform with fewer managed services, and per-resource pricing takes more thought than picking a named plan.
How to choose between them
- Choose Oracle Cloud if your workload is Egress-heavy workloads, Oracle Database, and teams optimising a bill rather than an ecosystem
- Choose Kamatera if your workload is Memory-heavy or CPU-heavy outliers, short-lived capacity, and multi-region deployments needing an unusual city
- Choose neither if the shape of the work does not match either — the full catalogue has eight other platforms, and the comparison tool will hold four of them side by side.
Related reading
- Buy Oracle Cloud Account – every Oracle Cloud configuration in stock
- Buy Kamatera Account – every Kamatera configuration in stock
- How to choose a cloud provider – the framework behind this comparison
- How cloud billing works – why the billing model matters more than the sticker price
- Compare up to four accounts side by side
Questions
Common questions about this comparison
Is Oracle Cloud cheaper than Kamatera?
The prices in the table above are the live catalogue prices for the accounts we stock, so you can compare those directly. Running cost is a separate question and depends on the billing model: Oracle Cloud bills per unit consumed and Kamatera bills a fixed monthly figure, which means the cheaper account is not always the cheaper month.
Can I run the same workload on both?
For ordinary Linux servers, databases and web applications, yes. The divergence starts when you adopt a platform's proprietary managed services — a specific queue, function runtime or identity model — because those are what make a migration expensive later.
Which one is better for Egress-heavy workloads?
That is Oracle Cloud's stated strength, so it is the natural starting point. It is still worth checking region availability and the billing model against your own constraints before committing.
What do I actually get when I buy an account here?
The configuration named on the product page and nothing beyond it — the vCPU figure, region, account age or credit exactly as listed. Both product pages set out every option in stock with its own price.