Last updated: September 25, 2026

About

Decentralized.Host lets independent operators run applications on hardware they control, coordinated by a control plane that can propose but never command.

Principles, each with an enforcement point

Self-hosted by default

A single-binary control plane and host agent. No SaaS dependency.

No telemetry, no phone-home

No outbound calls except the ones the operator configures.

Hosts remain sovereign

Local policy decides admission; the control plane can read it but never change it.

Desired ≠ admitted ≠ observed

Separate everywhere, end to end.

Every consequential transition is observable

Hash-chained ledgers on the control plane and on every host.

Offline operation is expected

Hold semantics, an outbox, buffered observations.

Failure is part of the product

17 chaos scenarios with invariants, run under traffic.

UNKNOWN remains UNKNOWN

Nothing unmeasured is estimated or implied.

The standard

Do not call a single control plane HA. Do not call a simulated failure chaos. Do not call a browser visualization mesh state. Do not call planned capabilities implemented. Do not publish numbers that were not measured.

This site follows the same rule. That is why it shows a recorded session instead of a simulator, labels every capability with its evidence, keeps failed validation attempts on the record, and says plainly that production readiness has not been demonstrated yet.

History

The name first belonged to a Python prototype: a FastAPI control plane scheduling Docker containers onto node agents behind Traefik. The Go implementation is a redesign around host sovereignty, signed evidence and a published protocol, built milestone by milestone (M1 sovereign runtime through M8 protocol conformance). It is now in production validation, which runs the same gate on real Linux machines before anything is called production-ready.