Hearth OSState must be rebuildable
Hearth assumes operators will eventually need to repair a service, move an installation, restore from failure, or rebuild from a known-good state.
Why self-host with Hearth
A platform for people who want to keep authority close.
Whether it runs on a home server, a VM, a private LAN appliance, or a public-facing VPS, Hearth keeps the same central idea: your infrastructure should be reproducible, maintainable, recoverable, identity-aware, and operator-directed.
Users are part of the appliance
Identity and authentication are not afterthoughts. They shape how access, content, and platform trust are organized.
The operator stays in charge
The platform is built to be fully directed by the person running it rather than drifting toward a managed-service dependency model.
What Hearth gives you
One system instead of scattered admin chores.
Reverse proxies, TLS, credentials, backups, restore paths, update flows, member access, commerce, and custom deployments stop living as unrelated operator burdens and start living inside one recognizable platform model.
Where it runs
Home server, VM, LAN appliance, or VPS.
Hearth is meant to remain coherent across deployment targets. The point is not a specific box. The point is to keep the system’s ownership, recoverability, and internal logic intact wherever you run it.