The common building blocks
Cloud platforms differ in naming and in detail, but nearly all of them expose the same four primitives: compute to run code, storage to keep data, networking to connect the two, and identity to decide who may do what. Almost every other service is a managed arrangement of those four.
Understanding the primitives is what makes platforms comparable. Once you know that you need two small instances, a managed database and a private network between them, you can price that shape on any provider rather than being steered by product names.
Managed versus self-managed
The same workload can usually be run two ways: assemble it yourself from raw instances, or let the provider operate a managed version of it. Self-managed gives more control and usually costs less per unit; managed costs more but removes patching, failover and backup work from your team.
Neither is automatically correct. Small teams tend to be better served by managed services for anything stateful, because the operational burden of running databases well is larger than it first appears.
Where accounts fit
An account is the boundary that holds all of this: the resources, the billing relationship and the permissions. Keeping separate accounts for separate projects is the simplest way to keep costs attributable and blast radius small.


