FlameNet DistributionsThe Mesh · .fyi
Sovereign Infrastructure

The Mesh — owned end to end, answerable to no one's cloud.

FlameNet's sites don't live on a hyperscaler. They live on a mesh of independent nodes we run ourselves, stitched together by encrypted tunnels, each carrying a full mirror of the content. If one node goes dark, the others keep serving. No CDN, no analytics vendor, no third party ever sits between you and the page.

Principles

What "sovereign" actually means here

Self-hosted

Every node is a machine we control directly — no managed platform, no vendor with a kill-switch over the content.

🔒

Encrypted between nodes

Nodes talk only over private encrypted tunnels. Replication never crosses the public internet in the clear.

Mirrored & resilient

Content is pushed from a source of truth to every node. Any node can serve the whole site; losing one doesn't take the site down.

Zero telemetry

Pages are pure HTML/CSS. No JavaScript, fonts, pixels, or CDNs — so there is nothing to phone home, by construction.

🔑

Own TLS, own certs

Each node holds its own certificate from a free public CA. Encryption is ours to issue and rotate, not rented.

Stewarded, not automated-away

Real people keep it healthy — patching, rotating keys, watching the lights. Accountability has a name.

How content reaches you

From source of truth to your browser

A deliberately boring pipeline — boring is what stays up.

01 · Source

Genesis mirror

Content is authored and held on a single source-of-truth node, kept offline-capable and backed up.

02 · Sync

Encrypted push

Changes are pushed to every public node over private tunnels — identical bytes everywhere, no drift.

03 · Serve

Independent nodes

Each node serves the full site on its own, with its own certificate. No shared point of failure.

04 · Reach

Failover DNS

Your request lands on a healthy node; if one is down, you're answered by another. You just see the page.

Node Status

The lights, in the open

A public view of the mesh — roles and regions only. For everyone's safety, exact addresses and keys are never published here. [Fill rows below with what you choose to disclose; keep it honest and current.]

NODESTATUS
Genesis mirrorSource of truth[region] operational
Edge node · [alias]Public serving[region] operational
Edge node · [alias]Public serving[region] operational
[add nodes as the mesh grows]
Why no IP addresses or keys? Transparency about how the mesh works does not mean publishing a target map. We disclose roles, regions, and health — the things that build trust — while keeping operational details (addresses, tunnel keys, topology) private, because protecting the mesh protects the people who depend on it.
Grow the mesh

Run a node. Become a steward.

The mesh gets stronger with every independent hand on it. If you run your own hardware and share the consent-first, zero-telemetry ethos, there's a place for you here. Stewards commit to keeping their node patched, honest, and extraction-free.

Become a steward Meet a steward