Skip to content
Greffon
Strategy

Self-Hosting vs Public Cloud: How to Choose in 2026

Cloud excels at elastic scale and managed services. Self-hosting wins on control, compliance, and predictable unit cost. In 2026, most teams need both.

GLGreffon Labs6 min read
control · elasticity · cost

Public cloud and self-hosting are not enemies. They are different tools with different sweet spots. The mistake is treating the choice as ideological. Decide it the way you decide any infrastructure question: against the constraints you actually have.

Start with the operating constraints

Map regulatory, latency, and data-sharing rules before comparing prices. If customer data cannot leave a country, a hyperscaler region is irrelevant unless it has the right attestations. Constraints narrow the field faster than any cost spreadsheet, so start there.

The decision matrix

Three dimensions decide most of it. For each one, here is how the two models actually behave:

1Control & compliance
Public cloudShared responsibility model; strong primitives, but still requires audits and legal reviews for new regions.
Self-hostingFull authority on residency and security layers, but you must operate the stack.
2Speed & elasticity
Public cloudMinutes to provision, every service exposed via API and IaC.
Self-hostingProvisioning speed depends on your automation layer. With Greffon, most apps deploy in under a minute.
3Cost visibility
Public cloudPay for what you use, but bills sprawl with egress and managed services.
Self-hostingCapEx or reserved hardware, but predictable. Ops time is the main hidden cost.

Hybrid becomes the default

Platforms such as Greffon let you run collaboration suites, developer tools, or analytics on your own hardware while tapping into public cloud for burst workloads. The question stops being which one and becomes which workload goes where.

When self-hosting is the right call

  • When data residency or sovereignty is non-negotiable: public sector, EU health, newsroom archives.
  • When network egress fees distort SaaS pricing versus owning the connection.
  • When you already run edge or on-prem compute for latency reasons and need the same experience as the cloud.
  • When a single team needs to ship a collaborative or developer tool to dozens of sites without opening tickets.

How Greffon helps

Greffon turns any machine into a greffer: a managed target that receives apps from a curated catalog. Click deploy, choose the greffer, and let the orchestrator handle secrets, TLS, and health checks.

The point is not to pick a side
It is to make self-hosting as fast to operate as the cloud, so the decision can be made on constraints and cost, not on how much DevOps each option demands.

If you want to see what that feels like, read how to self-host on a free Oracle Cloud server for a full setup, sharp edges and all.

GL
Greffon Labs
We build Greffon, the simplest way to turn any machine into a server you own.

Keep reading

~/blog/avoid-cloud-lock-in
Strategy

Avoiding Cloud Lock-In: A Playbook for Platform Teams

Keep your optionality while still delivering the experience your engineers and knowledge workers expect.

~/blog/gdpr-data-residency
Strategy

GDPR, Data Residency and Modern App Stacks

A practical guide to keeping collaboration and developer tools compliant without slowing teams down.

Ready to turn on your greffer?

Install in minutes. Deploy each app in seconds. Your server, your apps.

Read the docs