"Self-hosting" used to be the default — everyone ran their own server. Then cloud platforms made it easier to outsource everything. Now there's a quiet swing back: rising cloud bills, data privacy concerns, and better tooling have made self-hosting viable again for businesses that wouldn't have considered it five years ago.
So when does it actually make sense? Here's the framework we use with clients who ask.
Three places it usually wins
Internal tools and dashboards. If you're building a private dashboard for your team — sales, operations, analytics, inventory — self-hosting can dramatically simplify the security story. The whole thing lives behind your VPN or a Cloudflare Tunnel. No public endpoint, no third-party platform with your data, no monthly SaaS subscription that escalates as your team grows.
Data you genuinely can't put in the cloud. Some industries have compliance or contractual constraints — health, legal, certain financial data — where keeping things on a server you physically control is the simplest path to staying in bounds.
High-volume workloads with predictable usage. Cloud pricing is great until you have a workload that runs constantly. A $200/month dedicated server can match what you'd pay $1,500/month for on AWS, if your usage is steady enough to take advantage. AI inference is the newest example — running a local language model on your own hardware is often cheaper than per-token API pricing once you cross a usage threshold.
Three places it usually loses
Public-facing high-traffic sites. If your website needs to handle traffic spikes from a marketing campaign or press hit, cloud auto-scaling is hard to beat. Self-hosting works fine for steady traffic; it falls over on 10x bursts.
Anything with a global user base. A server in one location serves users near it well and users on the other side of the world poorly. Cloud platforms put your content in dozens of edge locations automatically.
Teams without ops capacity. Self-hosting means someone owns the server: patches, backups, security updates, hardware failure planning. If no one on your team has that skill set or that time, it's a liability waiting to happen.
How we use it ourselves
At App & Design we run a portion of our own infrastructure in-house — internal SaaS tools, client dashboards, staging environments, and a few production workloads where it made sense. We do this because we have the skill set, the time, and the genuine cost and control benefits at our scale. We're transparent with clients about which of their projects we self-host vs. which we put on managed cloud, and we make that decision per-project based on what's right for them.
For most clients we recommend the boring, reliable cloud setup: a fast VPS or managed host, with Cloudflare in front for caching and security. It's cheaper than AWS, simpler than on-prem, and works for 80% of business websites.
The middle path: Cloudflare Tunnel
One pattern that's worked really well for us: keep the application on a server you control (which can be on-prem or a small VPS), but expose it to the world through Cloudflare Tunnel. You get most of the benefits of self-hosting — control, predictable cost, no platform lock-in — while Cloudflare handles the public-facing concerns like DDoS protection and global edge caching. We use this for several internal tools and a handful of client projects.
The honest decision tree
- Is this a public-facing site that needs to handle traffic spikes? → Cloud.
- Is it an internal tool used by a small team? → Self-host (or use a managed platform if no one on your team can own the server).
- Is data residency or compliance a real constraint? → Self-host or carefully chosen regional cloud.
- Is your usage steady and high enough that cloud bills are eating margin? → Run the numbers on a dedicated server.
- None of the above? → Cloud. The convenience usually wins.
If you're thinking about how to host your next project and want a second opinion, get in touch. We'll give you a straight answer, including the cases where self-hosting would actively work against you.
Want to work with us?
If something here resonated, let's talk about what you're building.