The Self-Hosting Landscape in 2026
Self-hosting has never been more accessible. Between Docker, Compose, and a growing ecosystem of deployment tools, you no longer need a full-time DevOps engineer to run production workloads on your own servers. But the landscape is crowded, and picking the right tool depends on what you actually need: simplicity, control, cost predictability, or all three.
Quick Answer
The Competitors at a Glance
| Tool | Model | Best For | Biggest Limitation |
|---|---|---|---|
| Stacker | Open-source CLI + hosted platform | Deploying OSS projects, multi-service stacks | Newer ecosystem, smaller community |
| Vercel / Netlify | PaaS, usage-based pricing | Frontend apps, serverless functions | Not for databases or stateful workloads |
| Railway / Render | PaaS, per-service pricing | Full-stack apps with managed DBs | Unpredictable bills, platform lock-in |
| Coolify | Self-hosted OSS, free | Heroku-like PaaS on your own server | Must provision and maintain the server yourself |
| CapRover | Self-hosted OSS, free | Simple app hosting with a web UI | Single-server only, limited multi-stack support |
| Portainer | Self-hosted, free/enterprise | Managing existing Docker containers | Manages containers you already have — doesn't create them |
Stacker vs Vercel/Railway: Own Your Infrastructure
Vercel and Railway are excellent for getting started fast — push to Git, get a URL. But the tradeoffs compound over time:
- Pricing scales with usage, not value. A moderately busy app can cost $50-200/mo before you know it.
- You don't own the infrastructure. Migrating away means re-architecting your deployment.
- Limited to their supported stack. Want to run a Rust binary, an n8n workflow, or a custom Docker image? You're often out of luck or paying a premium.
With Stacker, you deploy to your own Hetzner, DigitalOcean, AWS, or on-premise server. You pay the cloud provider directly — Stacker manages the deployment, not the bill. A $5/mo Hetzner VPS running Stacker can replace $200/mo of PaaS services.
Stacker vs Coolify: Provisioning Included
Coolify is the most popular self-hosted PaaS. It gives you a Heroku-like dashboard on your own server. But there's a catch: Coolify requires you to already have a server running. You need to provision a VPS, install Docker, install Coolify, configure networking, and then start deploying apps. That's the part Coolify doesn't help with.
Stacker operates one layer below and above. It provisions the cloud server for you (from 8+ providers including Hetzner, DigitalOcean, AWS, Linode, Vultr, Contabo), deploys your stack, configures the reverse proxy and SSL, sets up monitoring, and installs a Status Panel agent for ongoing management.
You can use Coolify alongside Stacker — Stacker provisions the server, then Coolify manages day-2 operations. They complement each other.
Stacker vs CapRover: Multi-Service, Multi-Cloud
CapRover is a simple, single-server PaaS. Install it on one machine, deploy apps through a web UI. It works well for simple setups but hits walls when you need:
- Multi-server deployments (API on one machine, database on another)
- Complex multi-container stacks with service dependencies
- Cloud-provider portability (move from Hetzner to AWS without changing your deployment config)
- Pre-built templates for common stacks (n8n + Qdrant + Ollama, for example)
Stacker handles all of these with a single stacker.yml file. You define your stack once, and it deploys identically to any provider.
Where Stacker Is Unique
Six capabilities that no single competitor combines:
- Full lifecycle: Provision server → generate Dockerfiles → deploy → configure proxy/SSL → monitor → update. One CLI, end to end.
- Multi-cloud: 8+ providers (Hetzner, DO, Linode, Vultr, Contabo, AWS, OCI, OVH) plus your own server. Switch providers by changing one line.
- AI-powered config generation: Point at a GitHub repo, Stacker reads the README, compose file, and source to infer the full deployment config.
- No lock-in: You own the servers, SSH keys, and data. Stacker generates standard Docker Compose files you can use without the CLI.
- Status Panel agent: A lightweight agent runs on your server for health monitoring, log streaming, container restarts, and configuration updates — without SSH.
- Marketplace: 56+ pre-built stacks (n8n, Qdrant, Ollama, Supabase, Ghost, Umami, Plausible, etc.) deployable in one click. Creators earn 75% revenue share.
When to Use What
| Your Need | Best Tool | Why |
|---|---|---|
| Deploy a Next.js landing page | Vercel | Free tier, instant deploys, built-in analytics |
| Deploy a full-stack app with DB | Railway or Stacker | Railway for speed, Stacker for cost control |
| Self-host 10+ OSS tools on one server | Coolify | Web UI for managing many apps on a single machine |
| Deploy a complex multi-service stack (API + DB + cache + queue + AI) | Stacker | Auto-detects everything, provisions the server, one command |
| Manage existing Docker containers | Portainer | Purpose-built for container management, not deployment |
| Deploy any GitHub repo without reading the docs | Stacker | stacker init --from-github is unmatched |
The Bottom Line
Stacker isn't trying to be the best at everything. It's the best at one specific workflow: I found a project on GitHub, I want it running on my server, and I don't want to spend an hour configuring YAML. For everything else, use the right tool — but for that workflow, nothing else comes close.
Getting Started
# Install
curl -fsSL https://raw.githubusercontent.com/trydirect/stacker/main/install.sh | bash
# Deploy something
stacker init --from-github plausible/analytics --with-ai
stacker deploy --target localStacker CLI is MIT-licensed on GitHub. The managed platform is at try.direct.