What is self-hosting? Home server, VPS or your own Cloudflare account

The short answer

Self-hosting is running software yourself, on infrastructure you control, instead of paying a company to run it for you. The usual example is replacing a subscription app with an open-source one that you install, configure and keep updated. Wikipedia describes it as running a service on a private server under the administrator's control, and that server can be hardware you own or a rented remote machine. The classic case is a computer at home, but it is not the only place people do it.

What defines it is who operates the software. If you hold the data, the configuration and the upgrade decisions, you are self-hosting, whether the machine is under your desk, rented by the month or a set of services in your own cloud account.

Three places to self-host

Criterion	Home server	VPS	Your own Cloudflare account
What you run it on	A computer or small board you own	A virtual machine rented from a host	Workers and storage services (D1, KV, R2) under your Cloudflare login
Who patches the operating system	You	You	Cloudflare runs the platform; you still update the app code
Fixed cost	Hardware and electricity	A monthly rent	Can be zero on the free plan within its limits
Reachable from the internet	You set up networking, a domain and TLS	Public address included; you set up TLS	A workers.dev address or your domain, with TLS handled by the platform
Limits	Your hardware and home connection	The size of the VM you pay for	Plan limits on requests, CPU time and database rows
Software you can run	Almost anything, including Docker images	Almost anything, including Docker images	Apps written for Workers, or static sites on Cloudflare Pages; most self-hosted apps are neither
Moving away	Copy data and files	Copy data and files	Code may need changes because of platform-specific bindings
Backups	Yours	Yours	Yours

A home server gives the most control and the most chores. A VPS removes the hardware and the home network from the problem and keeps the rest. The Cloudflare route removes the server too, which is why it suits small, always-on tools, but it only works for software built for it: Workers apps, or static sites served from Cloudflare Pages.

Self-hosting on a home server

You install the application on a computer you own, usually with Docker, and reach it from other devices through your router and a domain, or through a private network. It suits people who enjoy running hardware and want data to stay physically in the house. The costs are power, noise, disk failures, a home connection that goes down, and the work of exposing a service safely. A good habit is to keep it private (reachable only on your own network or through a VPN) until you understand what you are publishing.

Self-hosting on a VPS

A virtual private server is a small machine you rent. You get a public address and uptime that does not depend on your home broadband, and you still own the operating system: updates, firewall, SSH access, certificates and backups. It is the most common route for Docker-based apps, and it fits software that needs a long-running process or a lot of memory. The monthly rent is the price of not buying and housing hardware.

Self-hosting on your own Cloudflare account

A third option exists for a narrower set of software. Some open-source projects are written to run on Cloudflare Workers and store data in Cloudflare D1 (SQL), KV (key-value) or R2 (object storage). You deploy them into your Cloudflare account, so you hold the data and the keys, and there is no virtual machine or operating system for you to maintain.

Cloudsteading catalogs these projects. Each listing shows the upstream README pinned to a commit, the license in plain English and an architecture diagram derived from the project's own configuration. Two examples of what that looks like:

• CloudMark is a bookmark manager. Our bookmark manager guide reads its pinned config and says what it covers and what it does not.
• Larafeed is a feed reader. Its pinned wrangler.jsonc declares a Worker, a D1 database, a KV namespace, three queues and a ten-minute cron, as covered in the RSS reader guide.

We read configuration and documentation. Cloudsteading does not claim to have installed, deployed or benchmarked these projects, and the images on a listing are upstream or documented-demo captures, not proof of a fresh deployment.

What the free plan allows (checked 2026-10-10)

"No server" does not mean "no limits". These are Cloudflare's published numbers on the date above; they can change.

Service	Free plan allowance	Source
Workers requests	100,000 a day	Workers limits
Workers CPU time	10 ms per request	Workers limits
Cron Triggers	5 per account	Workers limits
D1 rows read	5 million a day	D1 pricing
D1 rows written	100,000 a day	D1 pricing
D1 storage	5 GB total	D1 pricing
R2 Standard storage	10 GB-month, with no egress fee	R2 pricing

A personal bookmark list or a small team tool may stay well inside these numbers. A busy public site, or an app that runs many background jobs, may not. The Larafeed example shows how a single limit decides the answer: in the RSS guide, the free queue allowance, not the Worker, is the first thing to check. Do the same arithmetic for any project before you rely on it, and note that paid plans exist if you outgrow the free one.

The trade-offs, stated plainly

• Vendor lock-in. A Worker that uses D1, KV or R2 is tied to those services. A VPS app usually moves with a database dump; a Workers app may need code changes to leave Cloudflare. Look for a documented export before you store anything you cannot lose.
• Limited choice. Most well-known self-hosted apps expect a server and a Docker host. Only a subset has been written for Workers (or is a static site that Pages can serve), so the Cloudflare route is a smaller menu, not a replacement for the whole self-hosting world.
• Free is conditional. Whether a workload fits the free plan depends on its traffic and background work. We never treat free hosting as permanent.
• You still own the work. No operating system to patch does not mean no maintenance. You update the project, rotate secrets, back up the database and decide what is public.
• Not affiliated. Cloudsteading is not a hosting provider and is not affiliated with Cloudflare. Listings are upstream projects credited to their creators.

When each option fits

If you...	Look at	Why
want to learn, run many services and keep data in the house	Home server	Most flexibility, and you accept the hardware and network chores
need a Docker app that runs all the time and must be online reliably	VPS	Public address and uptime independent of your home connection
want one small tool such as a bookmark manager, feed reader or analytics script and do not want a machine to look after	Your own Cloudflare account	No server to patch, if a project exists for your job and fits the plan limits
need heavy compute, large databases or software with no Workers port	VPS or home server	Workers limits and the small catalog of compatible projects get in the way
are not ready to handle updates and backups	Stay on the SaaS	Self-hosting moves the maintenance to you

How to start, whichever route you choose

1. Pick the SaaS you want to replace and write down the three features you actually use. Our alternatives pages map open-source projects to the tools they replace.
2. Check the project's license before you deploy it for others. A permissive license such as MIT asks little; a network copyleft license such as AGPL v3 asks you to offer source to users of a modified copy. The license guides explain each in plain English.
3. Try it somewhere disposable first: a local container, a VPS you can delete, or a workers.dev address.
4. Export your data from the SaaS and import a small sample before moving everything.
5. Decide what is public and test it from a private browser window.
6. Set up backups and billing alerts before you depend on it.

Browse the Cloudsteading project directory to see which open-source projects can run on Cloudflare, or start from the bookmark manager and RSS reader guides.