Should you self-host or use a managed service?
The total cost of ownership math for self-hosted vs managed in 2026.
Self-hosting means you manage the server, the deployment, the backups, the security. Managed means you pay someone to do all of that. Both have a place. The wrong choice is expensive.
Where self-hosting wins
Cost at scale. A self-hosted WordPress site on a $20/month VPS can match what a managed WordPress host charges $50-200/month for. The difference compounds.
Full control. You can install any software, modify any configuration, run any service.
No vendor lock-in. The whole stack lives on your hardware (or rented hardware you control). Migrating providers is straightforward.
Specific compliance requirements. GDPR data residency, HIPAA, SOC 2 — sometimes easier to satisfy with self-hosted because you control the entire chain.
Where managed wins
Time. Managed services swallow the overhead that self-hosting demands. Updates, backups, security patches, monitoring, scaling — all included.
Reliability. A managed host has 24/7 ops people. You probably don't. When the site goes down at 3am, who's awake?
Performance defaults. Managed services optimise the stack for you. Self-hosting requires you to know what good looks like and configure accordingly.
Skip the rabbit hole. Self-hosting can become its own hobby. Every "why is this slow" turns into a weekend of investigation.
The honest math
Self-hosting only saves money if your time is worth less than the managed premium. For most small studios:
- Managed Vercel / Netlify / Webflow / Shopify: $20-200/month base, scaling with traffic.
- Self-hosted on Hetzner / DigitalOcean / Linode: $5-50/month base, plus your time.
If you spend 10 hours/year managing the self-hosted setup, and your time is worth $50/hour, you've spent $500 of effort to save $1000-2000 in fees. Maybe worth it.
If you spend 50 hours/year (more realistic when things go wrong), the math flips and managed wins by a lot.
The hybrid case
Most studios in 2026 mix both:
- Vercel / Netlify for the studio website (managed).
- A managed Postgres / MongoDB cloud database for any data.
- Self-hosted specific things that benefit from it (file storage on R2 instead of S3, a self-hosted analytics tool, a self-hosted CMS like Payload).
The mix lets you avoid the worst tax of either approach.
What changed in 2026
Managed services have gotten significantly better. Vercel, Cloudflare Workers, Supabase, and friends have closed most of the cost-vs-control gap. The "you have to self-host to get serious performance" argument doesn't hold the way it did in 2018.
At the same time, self-hosting has gotten easier. Coolify, Dokku, and similar tools make self-hosting feel like Heroku without the bill. For technical teams that enjoy this work, the experience is genuinely good.
The recommendation
If your studio doesn't have a dedicated dev-ops person, default to managed. The productivity gain is worth the premium.
If you have someone who enjoys infrastructure and can give it real attention, self-hosting saves money and gives more control. Just be honest about the time commitment.
The wrong move: self-hosting because it feels more legitimate, then resenting the time it takes when things break.