Skip to main content

Reviewed 2026-10-14 · 21 self-hostable tools

Software you can run on your own server

These are the tools that replace a subscription with a server you rent: analytics, automation, wikis, photo libraries, document archives, newsletters, dashboards and media servers. For each one we describe what it actually takes to run — the memory it wants, whether it is one container or four, what grows, and what you give up — and we link the project's own install documentation so you can read the source rather than our summary of it.

We do not print a figure for what self-hosting costs, because the number depends on the box you choose, the disk you need and the backup you keep. Instead every page ends at the providers' own pricing pages. What we will say plainly is what you are taking on.

Tools
21
Groups
9
Straightforward
3
Involved
5

Six costs that come with every tool below

Self-hosting moves work from a vendor's rota onto yours. None of it is optional, and it is the same for all 21 tools here, so it is stated once rather than repeated on every page.

  • You own the updates. Security releases have to be applied by you, on your schedule, and a project that stops publishing releases becomes your problem to notice.
  • You own the backups, and a backup is not a backup until you have restored from it once.
  • You own the uptime. There is no status page to watch and no support line to call when it stops answering.
  • You own the security patches, the TLS certificate, the reverse proxy and the firewall in front of it.
  • You are the on-call rota. The failure mode nobody plans for is being the only person who knows how the thing was set up.
  • The hardware has a running cost and a lifetime. Disks fail, and the replacement is on you.

Web & product analytics · 3

Analytics is the most common first self-host: the tracker is small, the data is sensitive, and the hosted plans are priced per event or per session.

Workflow automation · 2

Automation is billed per task or per run, so the bill tracks your success. Moving the runner onto your own box changes what a busy month costs.

Docs & knowledge bases · 4

A wiki or note store is small data and a lot of writing. Self-hosting keeps the content readable when a subscription lapses.

Files, photos & documents · 4

These are the entries where storage, not software, decides the outcome. Plan the disks and the backup before the install.

Email & publishing · 2

The software here is the easy half. Deliverability, DNS records and reputation are the parts that decide whether self-hosting this is a good idea.

Databases & dashboards · 2

Spreadsheet-databases and BI tools that read from where your data already lives, rather than replacing it.

Design & prototyping · 1

Design tools are heavy applications: editors, exporters and file storage. Expect a bigger box and more services than a wiki.

Developer & identity services · 2

Services a technical team can run for itself, where the data is source code or credentials and the case for control is strongest.

Media servers · 1

Software for your own film, television and music library. The server is cheap next to the disks that hold the library.

Where the server comes from

Every tool on this page runs on an ordinary virtual machine — a small server with root access. That is the purchase this section is really about. We do not print monthly figures, because the right size depends on the tool and on your data; the links below go to each provider's own pricing page so you can see the current numbers there.

Hostinger

Hostinger's VPS product is the closest fit to a self-hosted application: its own page advertises root access, Docker and NVMe storage, with data centres in several regions.

See Hostinger's plansRead Hostinger's published pricing ↗

DigitalOcean

Virtual machines billed as you use them, with separate volumes, snapshots and object storage for the parts you want to keep outside the server.

See DigitalOcean's plansRead DigitalOcean's published pricing ↗

Hetzner

Cloud instances and dedicated servers with rates published per instance size, so the cost of a bigger box is visible before you move.

See Hetzner's plansRead Hetzner's published pricing ↗

What to check on any provider's page

  • A virtual machine you have root on, not a website plan with a control panel bolted on top.
  • Snapshots or automated backups, and where those backups are stored.
  • Block storage or object storage for the data that will outgrow the server's own disk.
  • What the monthly rate renews at, rather than the first-term rate on the signup page.
  • Where the data centre is, if the data has a jurisdiction attached to it.

The “See plans” links go through our own /go/ redirect and some of them are affiliate links, which pay us if you sign up. That does not change what we write: the descriptions and trade-offs in this section come from the projects' own documentation, and the plain pricing link under each provider is not an affiliate link. See our disclosure.

Not ready to run a server?

That is a reasonable conclusion. 77 hosted tools are covered in the main index, with each vendor's own pricing page linked, and the head-to-head comparisons cover what actually differs between two products. Where a self-hosted tool has a hosted counterpart we track, its page links straight to our notes on it.

Spotted something out of date? Corrections go to [email protected].