Flare

What Flare will be

Today a self-hosted stack often leans on Cloudflare for the edge — a tunnel to expose services without opening ports, and DNS to point names at them. Flare brings that capability in-house and open: your own tunnels, your own DNS, your own mesh — no third party in the path.

• Secure tunnels. A cloudflared-style outbound tunnel: expose a service to the internet without opening inbound ports or running a public load balancer. The agent dials out; traffic rides the tunnel back to your cluster.
• DNS management. Create and manage the DNS records that point hostnames at your tunnels — the same "add a public hostname and it just resolves" flow, self-hosted.
• WireGuard mesh. Connect multiple self-hosted platforms over fast, encrypted WireGuard tunnels so they can reach each other privately.
• Platform-to-platform sync. The mesh is the substrate for syncing between instances — e.g. an Org Sync transfer or a reciprocal encrypted backup running over a private WireGuard link between two friends' Grown deployments, instead of over the public internet.

Why it matters

Self-hosting shouldn't mean depending on a hyperscaler for the network edge. Flare keeps the tunnel, the DNS, and the inter-platform mesh under your control — and turns "two separate instances" into "two instances that can securely talk and sync," which is what makes a federation of Grown deployments practical.

Status

Planned — not yet available.

Category

Admin & infrastructure

Builds on

WireGuard, tunneling, DNS