Live demo

Preview the platform before you run it.

The beta exists so visitors can feel Hearth as a coherent portal, not just read about it. It should answer the question “what is this like to use?” before the question “how do I install it?”

Launch live demo Why self-host this?

What you can experience

The beta is a limited live slice of the appliance.

It shows enough of Hearth to make the platform shape legible while running on smaller infrastructure than the full platform.

Dashboard and portal layoutUnderstand what the appliance feels like when identity, navigation, and platform surfaces all begin in one home base.
Native administrationPreview the fact that Hearth has its own operational layer instead of hiding everything behind third-party dashboards.
Codex and content systemsSee how managed reading, packages, and preserved source material become part of the platform itself.
Arcade and app-adjacent surfacesExperience the side of Hearth that feels inhabited, not just maintained.

How the demo should read

Limited access, real platform logic.

The goal is not to fake a read-only portal. The goal is to offer a smaller open beta where members can feel the real platform shape, native systems, and portal flow without exposing the full production appliance.

What comes next

After the demo, the real question is ownership.

Once someone understands the platform shape, the natural next step is understanding why Hearth is built to be self-hosted, recoverable, and operator-directed in the first place.

Next stop
Why ownership matters.

The Self-Hosting page explains why Hearth treats identity, recoverability, local direction, and durable operator control as central design constraints instead of optional extras.

Continue to Self-Hosting