Deployment & Infrastructure

What counts as deployment and infrastructure tooling?

This category covers everything between finished code and a running application: self-hosted PaaS platforms such as Coolify and Dokploy, container management such as Portainer, plus reverse proxies, monitoring agents and server utilities. The common denominator is almost always Docker. If you can package an application as a container, every tool in this category is open to you, from a one-person homelab to an agency server with thirty client projects.

The category has gained momentum in recent years because the question of where to host is being asked again. Vercel, Netlify and Heroku showed how comfortable deployment can be. Their pricing scales with your project's success, though, and the data sits with US providers. Self-hosted PaaS tools transfer exactly that comfort to your own server.

Typical use cases

Side projects on a VPS: A 5-euro server at a European provider, Coolify or Dokploy on top, and every git push deploys automatically. For hobby projects this replaces the free tiers of cloud services, without their limits.

Agencies and freelancers with client projects: One capable server instead of twenty separate hosting contracts. PaaS tools manage deployments, SSL certificates and databases per project in one place.

Teams with staging environments: Preview deployments per branch, familiar from Vercel, run on your own hardware with self-hosted tooling and without per-seat pricing.

Homelab as the entry point: Many people start with a home server for personal services and later carry the tooling into production. The tools are the same.

What matters when choosing

Calculate the operational effort honestly: A self-hosted PaaS takes deployments off your hands, but not the responsibility for the server underneath. Operating system updates, monitoring and security stay with you. If you have no time for that, treat the premium of a managed service as what it is: paid working time.

Backup strategy before the first deploy: The most important question for any infrastructure tool is how you get back after a failure. Automatic backups to external storage and one rehearsed restore belong to the setup, not to the retrofit.

Docker Compose compatibility: Tools that understand plain docker-compose keep you mobile. Proprietary configuration formats tie you to the tool, even when it is open source.

Update path and community: Infrastructure tools live on active development. A look at release frequency and community size says more than any feature list.

Digital sovereignty: the alternative to the hyperscalers

Hosting decisions now include decisions about data residency and dependencies. US cloud providers are subject to the CLOUD Act, which allows American authorities access to data regardless of where the servers stand. For personal data of European users this is a real factor in any GDPR assessment.

Combining a European cloud provider with open source deployment tooling solves both problems at once: the data stays under European law, and the tooling belongs to nobody who can change the pricing tomorrow. A VPS at a German or European provider costs a fraction of comparable hyperscaler resources, and tools like Coolify have made the comfort gap to Vercel and Heroku small.

Frequently asked questions

What is a self-hosted PaaS?

Platform-as-a-service software you install on your own server: git push deployments, automatic SSL certificates, database management and logs in one interface. Coolify and Dokploy are the best-known open source representatives. You get the Heroku experience but only pay for the server.

Do I need Kubernetes?

For the vast majority of projects: no. Kubernetes solves problems that only appear with many servers and teams, and charges considerable complexity for it. A single server with Docker Compose and a PaaS tool carries surprisingly large loads. Switching later remains possible once the requirements have become real.

What does hosting with European providers give me?

Three things: data residency under European law instead of CLOUD Act exposure, predictable fixed prices instead of usage-based billing, and lower latency for European users. For GDPR-relevant applications, an EU location also simplifies all privacy documentation.

The tools above range from complete PaaS platforms to specialised utilities. Each detail page explains which setup a tool suits and which alternatives exist.