A clear control plane for infrastructure you operate.
Hearth Platform is being developed as a self-hosted infrastructure management platform, beginning with game server workloads and a deliberate separation between central coordination and node execution.
A central view. Execution close to the machines.
The architecture separates the management interface and API from the daemon that works with local infrastructure. The design shown here reflects the intended system boundaries; capabilities remain subject to implementation.
Familiar foundations.
Purposeful boundaries.
A pragmatic stack gives the platform room to develop across the web, API and infrastructure layers. These are the technologies identified for the platform; this does not imply every capability is complete.
Built for today. Designed for tomorrow.
These principles guide the technical direction as the platform is developed.
Self-hosted by design
The intended deployment model keeps operators close to their own infrastructure.
Explicit boundaries
Central coordination and node-level execution have distinct responsibilities.
API-first direction
A consistent API can support the web experience and future integrations.
Permissions matter
Access control and safe operation are core concerns in infrastructure tooling.
Multi-node direction
The architecture is intended to extend beyond a single machine as the platform matures.
Infrastructure independence
Build toward flexibility across environments rather than assuming one provider.
An active development project.
Hearth Platform is currently in development. The architecture and technology choices describe the product’s direction, while individual functions and integrations must be implemented and validated before being presented as available.
Building infrastructure software?
We’re interested in exchanging ideas with operators, developers and technology partners.