Hearth OSThe platform spine
Compose orchestration, Caddy ingress, LLDAP directory authority, Dex federation, and local-first hostname behavior establish the appliance foundation.
What ships with Hearth OS 1.0.0 Community Beta
A practical, operator-first feature surface.
The feature set is not random stack accumulation. Each layer exists because it supports Hearth’s platform model: centralized identity, unified ingress, recoverable state, native administrative ownership, and extensibility without chaos.
The operator surface
Install, update, backup, restore, database, storage, and service views live inside Hearth instead of being scattered across dashboards.
The growth model
Custom apps, custom stacks, package systems, and content workflows are meant to plug into a recognizable platform pattern.
Infrastructure and identity
- Docker Compose-based stack orchestration
- Centralized ingress and TLS through Caddy
- LLDAP as the primary directory authority
- Dex for SSO and OIDC federation
Native administrative surfaces
- First-party Hearth admin portal
- Stack install, update, backup, and restore controls
- Docs and manual surfaces inside Hearth
- Database, storage, and service management views
Content and publishing systems
- Nexus site and content workflows
- Protected member-facing routes
- Hearth Codex as a managed reading subsystem
- HCodex as a portable package format
Commerce and access control
- Medusa-based headless commerce
- Hearth Vault for digital fulfillment
- Hearth-managed entitlements and access logic
- Recurring and one-time membership support
Custom deployment workflows
- Custom Install for first-class Compose stacks
- App Compiler support for Next.js, React, Node.js, Vue, and static sites
- Deployable custom apps as managed stacks
- A path for growth without operational drift
Gaming and media-adjacent systems
- Hearth Arcade on a Hearth-owned compatibility layer
- Hearth Sync-backed save-state workflows
- Controller bypass support for custom mappings
- Local ROM feed handling through Hearth media paths
Operational boundaries
Authority is separated on purpose.
Hearth intentionally separates concerns across infrastructure lifecycle, ingress, identity, commerce, entitlements, protected content, fulfillment, Codex packaging, and app deployment. That separation is one of the defining design choices in the platform.
Membership rule
The commerce engine owns the transaction.
Hearth owns entitlement, authentication, and protected access after purchase or grant. That is how the platform keeps commerce integrated without surrendering the access layer.