What Should You Self-Host—and What Should You Leave to a Professional Provider?

The right question is not “Can this be self-hosted?”

A great many services can.

The useful question is whether you want to become the person responsible when that particular service is down, compromised or unrecoverable.

Score the consequences first

Before choosing software, ask four questions.

What happens if the service is unavailable for a day? What happens if its data is lost? What happens if it is breached? How difficult is it to restore correctly?

A media server and a password vault can both run on Linux, but their failure consequences are nowhere near the same.

Good candidates usually tolerate downtime

Self-hosting is easiest to justify when temporary failure is inconvenient rather than catastrophic.

Home automation, local media, experimental development tools and some personal file or photo services can be reasonable candidates when backups and manual fallbacks exist.

They provide useful control without requiring carrier-grade uptime.

Backups must be understandable

A service is easier to own when you can clearly identify its data, configuration and database and can test a restoration.

If recovery requires a pile of undocumented state that only exists on the live server, the maintenance burden is already telling you something.

Remote exposure changes the equation

A LAN-only service has a different risk profile from a public service exposed to the internet.

Public applications need ongoing patching, authentication, TLS, monitoring and careful network design.

The phrase “runs in Docker” is not a security plan.

Use much more caution with high-consequence systems

Password infrastructure, public customer-facing applications, systems holding regulated or highly sensitive data, and services that depend on dependable external delivery or reputation all deserve a higher bar.

That does not mean self-hosting them is impossible.

It means the operator needs the skill, time, backup plan, monitoring and recovery process appropriate to the consequence.

Hosted providers fail too

Outsourcing does not eliminate outages or mistakes.

It changes which operational responsibilities you retain and which you delegate.

A professionally operated service can be the better choice when availability, security maintenance, abuse handling, deliverability or compliance work would otherwise become a second job.

Self-host when control solves a real problem

Useful reasons include keeping selected data on equipment you control, avoiding a fragile vendor dependency, integrating local services, reducing recurring cost in a workload you understand, or supporting local AI and automation.

“I can” is not enough.

A mixed approach is often stronger

You can self-host files while using a professional email provider.

You can run local home automation while keeping an off-site commercial backup.

You can run a local AI model while using hosted services for public customer communication.

There is no prize for achieving cloud purity.

Why Self-Hosting Matters More in the Age of AI explains the control argument. Running Your Own Password Manager at Home: Benefits and Risks shows why high-consequence services need a stricter decision.