Cloud

Rent compute, storage and networking elastically instead of owning servers.

This hub collects the blocks of the cloud layer: the hyperscalers, the friendly challengers, the platform services that sit on top, and the primitives, object storage, DNS, CDNs, that almost every product consumes from someone.

Why it matters to an indie builder: nearly all cloud decisions are really three. Where compute runs, a PaaS for speed or raw instances for control. Where state lives, managed Postgres versus a database platform. And what fronts it all, usually a CDN with TLS. Getting those three right matters more than the vendor logo, and the differences between vendors are mostly price, ecosystem depth and how much of operations they absorb.

A realistic choice pattern: start on a PaaS with managed Postgres behind a CDN, and move specific pieces, compute-hungry workers, cheap bulk storage, to specialists as bills and traffic justify the operational cost of more vendors.

The trade-off of cloud breadth is complexity billed by the hour; every managed service removes work and adds a line item. The listings here make the price of that trade explicit per provider.