Cloud computing changes who operates each layer. It does not remove the layers.
Start with a computer
A web application needs somewhere to run. That place has a processor, memory, storage, and a network connection. A cloud provider makes those resources available over a network, usually through an API or dashboard. You rent access instead of buying and maintaining every physical machine yourself.
A virtual machine is one common starting point. It behaves like a separate computer even though it may share physical hardware with other virtual machines. You choose a size, install software, and pay according to the provider’s terms. “Serverless” services move more of that administration to a provider; servers still execute the work.
Infrastructure, platforms and applications
Infrastructure supplies compute, storage, and networking. With a virtual machine, you usually manage the operating system and application yourself.
A platform helps build, deploy, connect, and operate applications on that infrastructure. It can provide defaults and automate deployment tasks. You still manage application behavior, data, and access.
An application service provides the finished software. You configure and use it, rather than deploy its implementation. The exact division of responsibilities depends on the service, not just its category name.
Check who maintains each part
Ask which party applies system updates, restores data, rotates credentials, controls network access, and responds when something fails. A provider may manage a database process while you still choose who can read the records and how long they should be retained.
Costs can include compute time, storage, backups, network egress, and services around the workload. An idle server may still cost money. Before choosing a plan, understand what is metered and what happens when you exceed a limit.
Where Hakopod fits
Self-hosted Hakopod is an application platform on infrastructure you operate. Its dashboard, CLI, and API help manage applications and their services. The operator still owns the cluster, storage, updates, and recovery.
Hakopod Cloud is in development and account signup is open. It provides a hosted dashboard and control plane. An account does not guarantee compute allocation or enable every planned feature. BYOD server capacity and the provider bill remain separate; paid checkout is not open yet. Managed databases need eligible workspace capacity and setup.
Try the idea
Draw four boxes: your application, its database, the server, and the platform managing deployments. Write an owner beside each. If no one owns database recovery, assign that responsibility before you deploy.
If a provider manages the server, does it automatically own your application backups?
Reveal the answer
No. Backup coverage, retention, recovery keys, and restore responsibilities depend on the service agreement and configuration. Make those responsibilities explicit and rehearse the restore.