One platform. One identity. Your infrastructure.

A self-hosted platform with an operating model.

Hearth makes a self-hosted server feel like a coherent environment instead of a pile of unrelated containers. Identity, ingress, recovery, administration, content, access, and extensibility live inside one durable platform model.

Identity-aware Recoverable Operator-first Extensible
Operating model
Identity, routing, recovery
What Hearth is Infrastructure with an internal logic

Hearth does not try to replace existing solutions. It gives those tools one coherent place to shine.

What Hearth does

It pulls operational ownership back into one place.

Instead of manually stitching together reverse proxies, TLS, identity, application credentials, backup paths, restore flows, commerce, and custom deployments, Hearth gathers those concerns into one platform model.

Identity

Users are part of the platform

LLDAP and Dex form the identity spine so access policy and authentication are not fragmented across random stacks.

Ingress

Routes are part of the platform

Caddy provides one ingress model for TLS, hostname behavior, and public exposure instead of letting every service invent its own pattern.

Recovery

State is treated as recoverable

Backups, restores, snapshots, and migration paths are first-class concerns because real operators eventually need to repair, move, or rebuild.

What ships with it

The practical feature set behind the platform.

Hearth OS 1.0.0 Community Beta is built around a concrete operator-first scope: infrastructure, administrative surfaces, publishing, protected access, commerce, deployment workflows, and Hearth-owned content systems.

Infrastructure and identity

Compose orchestration, Caddy ingress, LLDAP directory authority, Dex federation, and local-first hostname workflows.

Native administrative surfaces

A first-party admin portal for installs, updates, backups, restores, databases, storage, and service management.

Content and publishing

Nexus site workflows, protected content routes, Hearth Codex, and HCodex package-based content ingestion.

Commerce and access control

Medusa transactions, Hearth Vault fulfillment, Hearth-managed entitlements, memberships, and activation workflows.

Custom deployment workflows

Custom Install for Compose stacks plus App Compiler support for Next.js, React, Node.js, Vue, and static deployments.

Gaming and media-adjacent systems

Hearth Arcade, Hearth Sync-backed save-state workflows, controller bypass support, and local ROM feed handling.

Live demo

See the platform in motion before you install it.

The live beta is the fastest way to understand how Hearth actually feels. Open the portal, walk the surfaces, and see how admin, apps, Codex, Arcade, and protected content live together as one system.

Limited open beta Portal-first tour Smaller live server

What to preview

Dashboard and admin Get a feel for the operating surface that makes Hearth more than a launcher for containers.
Codex, Arcade, and apps Preview the native systems that give the platform memory, play, and an expanding application layer.
Next stop
Why Hearth exists.

The next page explains the philosophy behind Hearth, what problem it is really trying to solve, and why it treats identity, recovery, access, and native workflows as platform concerns.

Continue to About