I would define hosting in the cloud as "self-hosting" because you perform the act of hosting that thing and thus have full control over it.
Yes it's not the same as hosting as your own hardware but I would argue that it accomplishes the same goals. The goal is to get other people out of your data. With a "service" the underlying company has every incentive to look at your data and use that to improve it's service, but when you host something yourself with a provider, it's in that providers best interest to never look at your data.
For me it all comes down to the goals of the people your are doing business with. With Cloudflare at least, their goal is to just upsell me on hosting equipment, they couldn't give a rats ass what I'm hosting on that hardware so long it's not illegal.
"Self-hosting is the practice of running a website or service on a home server instead of a web hosting service outside of the administrator's own control."
And then basically contradicts itself in the next paragraph:
"The practice of self-hosting web services became more feasible with the development of cloud computing and virtualization technologies, which enabled users to run their own servers on remote hardware or virtual machines."
In any case, I think the generally accepted definition of self-hosting has expanded over the years to include software that you're running on rented hardware in someone else's data center.
I would describe it as externally hosted yet managed specifically because someone else is most likely, whether they admit to it or not, recording some sort of logs on my service and data and that is a choice that I do not own or, in some cases, have access to.
It is confusing, I agree. IMO we should have "self-running" and "self-hosting". Self-running if I provide the hardware, self-hosting if I manage it. Or swap the term, still not sure but there is a difference between you are the one maintaining it and where does it run.
I gave it a second thought and I think terms should be "self-managed" - you manage it either locally or in cloud and "self-hosted" you host it locally. Idk "self-contained" doesn't click with me, to be fair.
I think it's a pretty clear line. Self hosted means you can run it locally in your home, using a saas platform or vps is just a convenience, not a requirement.
What about FOSS SaaS alternatives that are meant for team collab? Like Plane (Jira replacement). Does that have to be ran locally at home for it to be considered "self hosted"?
Self hosted means you host it yourself. I.e. you run the software. Running on your own home machine is definitely self-hosted. Hosting it on a VPS in some datacenter still is. Running it in a cloud platform somewhere is stretching it but I'd say that sill is. SaaS definitely is not self hosting even if the software is open source. The important part is that you're the one in control of the software.
No, crazy would be owning the router and cables/satellites as well as producing your own power and having a manufacturing plant for hardware capable of running the software.
Careful with Cloudflare's "free" AI tier if you use paid workers. I was never able to get an answer on why I was billed for their confusing neuron usage for stuff that should have been covered under their usage limits. Their customer support just ignored my ticket. Apparently it's a known issue that they don't give a shit based on discussions in their support Discord.
Not disagreeing because I don’t know anything about this particular situation, but I think if you look at any company’s support discord, you will find that they don’t give a shit because of the sample bias. People whose problems they solved. Don’t end up there.
For those questioning (rightly) the "self-hosted" description, I suspect its a poorly-worded attempt to clarify there is no third-party requirement (eg. the repo is not cloudflare-owned) beyond your own cloudflare account.
Sometimes these "open source" services are a bit misleading as there is a coupling to the org providing them; I think the OP here just means there's nothing extra needed beyond whatever cloudflare commitment you already have.
Did a side project on Workers and the self host test for me was whether I could run it off Cloudflare at all. Durable Objects and KV bindings meant no, so it was really just deploy it yourself.
Hi HN! I built Talorys, an open-source personal AI agent that runs entirely in your own Cloudflare account.
The idea came from wanting a personal AI assistant that I could own and control, without paying a monthly subscription or relying on someone else's hosted service.
Talorys uses Cloudflare Workers, Workers AI, Durable Objects, and Pages to provide:
AI chat with persistent memory and conversation history
Task, note, and project management
Scheduled reminders and recurring automations
A responsive web interface accessible from any device
Password-protected access with no signup or external accounts
One-command deployment: npx create-talorys@latest
Everything runs in your Cloudflare account. Your data stays under your control, and there's no telemetry or third-party backend operated by me.
It's designed to work within Cloudflare's free-tier limits for personal use. You don't need to manage a VPS, database server, or Docker containers.
The biggest challenge was making deployment simple enough that someone could set up their own AI assistant without manually configuring Cloudflare services.
The project is still early, and I'd love feedback from the HN community, especially on the architecture, security, and what would make a self-hosted personal AI agent genuinely useful.
This is a neat implementation, regardless of the argument over how it is hosted! There are a number of other systems along the same general lines, but for me the sticking point is that there is no good implementation equivalent to the Alexa devices scattered around my home (and RV!) that allow me to interact via speech. I'm working on one of those now in my copious spare time. (Yes, there are a bunch of rPi projects. Their rates of errors are unacceptably high.)
I'm torn in situations like these, because OP is clearly furthering societal trends that are objectively harmful by watering down terminology like this.
It is snark, but it is immune-response snark and not petty snark.
One shouldn't crush them for it, as it might be driven by naivety, but soft politeness alone doesn't steer us away from harmful ideas.
Social friction caused by feeling stupid for saying something is an important tool if wielded with responsibility and not just swung for ego.
> without paying a monthly subscription or relying on someone else's hosted service.
But you are hosting it on Cloudflare? There is always a cost when running on someone else's platform that advertises itself as 'free-tier' and it can change at any moment.
Yes it's not the same as hosting as your own hardware but I would argue that it accomplishes the same goals. The goal is to get other people out of your data. With a "service" the underlying company has every incentive to look at your data and use that to improve it's service, but when you host something yourself with a provider, it's in that providers best interest to never look at your data.
For me it all comes down to the goals of the people your are doing business with. With Cloudflare at least, their goal is to just upsell me on hosting equipment, they couldn't give a rats ass what I'm hosting on that hardware so long it's not illegal.
If the software can be switched to a rented or purchased hardware (I do not want Cloudflare's offering) then it is "self-host-able" IMO.
I think there are open source Cloudflare alternative hosting software.
The first sentence states:
"Self-hosting is the practice of running a website or service on a home server instead of a web hosting service outside of the administrator's own control."
And then basically contradicts itself in the next paragraph:
"The practice of self-hosting web services became more feasible with the development of cloud computing and virtualization technologies, which enabled users to run their own servers on remote hardware or virtual machines."
In any case, I think the generally accepted definition of self-hosting has expanded over the years to include software that you're running on rented hardware in someone else's data center.
I would describe it as externally hosted yet managed specifically because someone else is most likely, whether they admit to it or not, recording some sort of logs on my service and data and that is a choice that I do not own or, in some cases, have access to.
Whether you use the cloud, or a vps, or a dedicated bare metal server, or your own equipment at home is all self hosting.
Sometimes these "open source" services are a bit misleading as there is a coupling to the org providing them; I think the OP here just means there's nothing extra needed beyond whatever cloudflare commitment you already have.
With `@cf/qwen/qwen3.8-27b` it's 240K input tokens and 34,000 output tokens
The idea came from wanting a personal AI assistant that I could own and control, without paying a monthly subscription or relying on someone else's hosted service.
Talorys uses Cloudflare Workers, Workers AI, Durable Objects, and Pages to provide:
AI chat with persistent memory and conversation history Task, note, and project management Scheduled reminders and recurring automations A responsive web interface accessible from any device Password-protected access with no signup or external accounts One-command deployment: npx create-talorys@latest Everything runs in your Cloudflare account. Your data stays under your control, and there's no telemetry or third-party backend operated by me.
It's designed to work within Cloudflare's free-tier limits for personal use. You don't need to manage a VPS, database server, or Docker containers.
The biggest challenge was making deployment simple enough that someone could set up their own AI assistant without manually configuring Cloudflare services.
The project is still early, and I'd love feedback from the HN community, especially on the architecture, security, and what would make a self-hosted personal AI agent genuinely useful.
GitHub: https://github.com/rociiu/talorys
It's MIT licensed. Contributions and suggestions are welcome!
https://news.ycombinator.com/newsguidelines.html
It is snark, but it is immune-response snark and not petty snark.
One shouldn't crush them for it, as it might be driven by naivety, but soft politeness alone doesn't steer us away from harmful ideas.
Social friction caused by feeling stupid for saying something is an important tool if wielded with responsibility and not just swung for ego.
But you are hosting it on Cloudflare? There is always a cost when running on someone else's platform that advertises itself as 'free-tier' and it can change at any moment.