Hearth OSWhat Hearth is
A full-stack self-hosting environment.
Hearth is designed around operational ownership. It is meant to be reproducible, maintainable, recoverable, identity-aware, extensible, and fully self-directed by the person operating it.
Why Hearth exists
Because infrastructure needs a shape.
Plenty of self-hosted projects can install applications. Hearth is solving the platform problem around them: identity, authentication, routing, data location, restores, and protected access.
What it is not
Not just a launcher for containers.
The point of Hearth is not to reinvent every application it ships with. The point is to give the operator one durable system for identity, routing, storage, recovery, administration, and extensibility while still standing on proven open-source software.
What makes it different
It treats platform concerns as first-class.
This is why Hearth includes native administrative surfaces and why systems like memberships, Vault, Codex, Nexus, and the App Compiler are treated as native surfaces instead of one-off integrations.
Users are central
Authentication and access policy should not be spread across stacks unless a stack truly requires it.
Failure is assumed
Restore paths, snapshots, and migrations are part of the design because real operators eventually need them.
Hearth owns Hearth workflows
Entitlements, protected access, Codex packaging, and app compilation belong in platform-owned surfaces.