Get access↗
Substrate · provider-operated

Biome.
A mesh of independent providers.

Biome is the decentralized substrate of Omega — community-operated clusters that opt into the mesh. Workloads address branes by manifest name; peers find each other through Tailscale, NetBird, or any WireGuard overlay you bring. There is no etcd, no scheduler, no API server. The mesh is the control plane; the manifest is the API.

[substrate]
Biome · provider-operated
[capability]
Standard (WASM)
[transport]
libp2p · QUIC · WG
[discovery]
mDNS · DNS-SD · static
The shape of biome

A mesh that
heals itself.

< 80 ms
peer convergence (P50)

Add a host, reach steady state in under 80ms on a 64-peer mesh.

0
single points of failure

The mesh is the control plane. Lose any peer; the rest re-route.

WAN
okay

Biome runs over Tailscale Funnel, NetBird, or any WG mesh you bring.

100K
msgs/s/peer

QUIC streams, framed; back-pressure aware; per-edge priority queues.

Manifest

Declare a peer pool,
point at your network.

// transform pool joins the mesh on boot, talks ingest→archive over edges
biome-pool.zgraph.tomlΩ · ZGraph
[brane.transform]
substrate   = "biome"
capability  = "standard"
peers       = "lab.lan/transform-pool-*"
replicas    = "auto"

[brane.transform.discovery]
mode        = "tailscale"
bootstrap   = "transform-pool-001.lab.lan"

[brane.transform.network]
overlay     = "wg-prod"
quic_port   = 7842
mdns        = true

[brane.transform.state]
crdt        = "rga"        # replicated growable array
fanout      = 8
gc_interval = "30s"
// annotations

peers is a glob that matches Tailscale node names. mDNS / DNS-SD / static lists also supported.

discovery.bootstrap is the first peer to gossip with. After convergence, peers are self-evident.

Operations

Watch the mesh
like a power grid.

$ω biome peers --brane transform
peer status rtt load edges transform-pool-001 ● HEAD 2ms 0.31 in:42 out:38 transform-pool-002 ● TAIL 5ms 0.28 in:41 out:39 transform-pool-003 ● TAIL 11ms 0.25 in:40 out:42 transform-pool-004 ◯ HEAL 21ms — reconciling
$ω biome trace 'tensor.shard:b3:9af2'
13:41:09.812 ingest.018 → transform-pool-001 2.1KiB 13:41:09.814 pool-001 → pool-002.local sync_ack 13:41:09.819 pool-001 → archive.nas-01 1.3KiB compressed 13:41:09.821 TRACE end 2 hops · 9ms wall · ed25519:RJk...
// rules
discovery
Tailscale · NetBird · mDNS · DNS-SD · static
transport
QUIC streams · framed · TLS 1.3
state replication
CRDT per-brane · GC at fanout
failure detection
phi accrual + gossip-driven heartbeats
partitions
quorum-free · last-writer-wins by signed time
Use it for

What Biome
is best at.

Long-running, stateful workers

Pool of agents, transformers, replay nodes — anything that benefits from cross-host state and survives a restart.
WORKERS

Cross-machine choreography

Branes on your laptop talking to branes in production talking to branes on a Pi in your closet — same address space, different physics.
HYBRID

Air-gapped operation

Biome doesn't phone home. Bring your own discovery, your own overlay, your own auth — the substrate doesn't care.
OFFLINE

Provider economics

Anyone with spare hardware can run a Biome cluster. Earn against workloads scheduled to your pool. Settlement is signed and on-chain-ready.
DePIN
← GaiaNext substrate — Habitat →