Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I agree with you.

and so does the author, kind of...

"And so, here is a gentle introduction to self-hosting that is not "true self-hosting", but whatever. Sue me."

:)



> Sue me

Or read an HN thread on "true self-hosting", https://news.ycombinator.com/item?id=41440855#41460999


They did not built their CPU from scratch, so this is not self hosting to me - they do not completely own the hardware.

Why arguing on semantics?


The difference is more than semantics, but there will always be vendor innovation to blur boundaries.


No it is not. I self-host on my hardware and regularly consider moving some services to a VM hosted by someone else. It would still be self-hosting because I am in control of the service.

If you want to have a truly service "by you" this is going to be complicated to rewrite (or review) the applications and OS and build your own hardware from something arbitrarily defined as "scratch".

It sounds very much like the discussions of audiophiles about golden cables and what not - while others listen to the music for the pleasure of listening.


> VM hosted by someone else ... would still be self-hosting because I am in control of the service.

A hosting vendor will have detailed "Terms of Service" by jurisdiction, self-hosting will not.

> complicated to rewrite (or review) the applications ... build your own hardware from scratch

There are options between those two extreme scenarios, many discussed at length in HN self-hosting threads.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: