Cloud library

Find and compare cloud services.

Explore a service category, review a product, or compare the options on your shortlist.

Find the service your app needs.

Start with a capability, then review the products that provide it.

Compare the options on your shortlist.

Filter by decision type, then open a comparison on your shortlist.

Providers

Coming soon

Explore cloud platforms and the services they offer.

Tools

Coming soon

Find tools for monitoring, deployment, and running your app.

Locations

Coming soon

Find cloud services available in your deployment country.

Stacks

Coming soon

Explore the services needed for common application stacks.

Calculator

Coming soon

Estimate running costs from your services, location, and expected usage.

Updates

Coming soon

Follow changes to the cloud data and comparisons.

How we compare cloud services.

What these comparisons cover

The current collection covers managed PostgreSQL on AWS, Azure, and Oracle Cloud. It compares billing components and selected operating features. It does not provide regional price quotes, capacity guarantees, benchmarks, or a calculated monthly bill.

Country comparisons will be added only after the exact service and feature availability have been checked. A provider's presence in a country does not establish that every service or backup option is available there.

Sources and checked dates

Each comparison-table entry links to the official source supporting it. The table shows the date those sources were checked. A checked date records our review; it is not the provider's price-effective date.

We summarize the documented feature or billing rule. Our recommendations are identified as recommendations in the page text. Provider documentation remains the reference when a service changes.

Comparing prices fairly

A future price example must specify the region, currency, runtime, compute configuration, storage, backup policy, and availability setup. It must list included components and omitted costs.

Missing prices remain missing. We will label an incomplete estimate as a subtotal. Trials, credits, and commitment discounts will be separate from the recurring baseline.

Equal memory or logical CPU counts do not prove equal performance. We will explain configuration differences rather than convert them into unsupported performance claims.

Review and corrections

The planned review cadence is twice a month. A maintenance owner must be assigned before public release. Changes to source data must update every affected comparison from the same shared records.

If you find an error, send the page link and the relevant official source to Hapy. We will review the evidence before changing the record.

Why Hapy publishes these guides

Hapy designs and builds applications. These comparisons help founders and small teams prepare infrastructure decisions. Enquiries about implementation are optional; reading the comparison does not require an account or email submission.