Get access↗
Substrate · customer-owned

Habitat.
Your metal. Your rules.

Habitat is the substrate where the host belongs to you. Phones, Pis, RISC-V boards, racks, the laptop on your desk. The omega-edge-agent joins the mesh, signs in with your tenant key, and starts answering on its declared edges. The same manifest that runs in our cloud runs in your closet — and the substrate doesn't notice the difference.

[substrate]
Habitat · customer-owned
[capability]
Standard (WASM)
[agent]
omega-edge-agent · <5MB
[arch]
ARM · x86 · RISC-V
What it runs on

From a phone
to a rack.

<5 MB
agent footprint

Static binary. No JVM, no container runtime, no daemon stack.

3
architectures

x86_64, aarch64, riscv64. Termux-tested on Android, Pi 4/5, Visionfive 2.

0
phone-home requirements

Air-gappable. Run a fully-isolated mesh on a closed LAN.

∞
hosts per tenant

Bring as many. Cost scales with workloads, not with hostnames.

Manifest

Pin a brane
to your hardware.

// archive workloads pinned to your local NAS, addressable on the substrate
habitat-rack.zgraph.tomlΩ · ZGraph
[brane.archive]
substrate   = "habitat"
capability  = "standard"
hosts       = ["nas-01", "nas-02", "nas-03"]

[brane.archive.agent]
binary      = "omega-edge-agent"
auth        = "tenant-key:ed25519:RJ4P..."
overlay     = "tailscale"             # or wg / netbird / lan

[brane.archive.storage]
local       = "/mnt/cold"
quota       = "8 TiB"
encryption  = "age-x25519"

[brane.archive.lifecycle]
boot        = "on-demand"
sleep_idle  = "5m"
// annotations

hosts can be a static list, a glob, or a label query. The agent runs on each host and reports its capacity.

Habitat hosts are tenant-scoped — the substrate enforces that no cross-tenant workload ever touches your hardware. The boundary is cryptographic, not just policy.

Operations

Onboard a host
in three commands.

$curl -fsSL omega.run/install | sh
✓ omega-edge-agent v0.1.0 installed → /usr/local/bin/omega-edge ✓ wrote /etc/omega/agent.toml (placeholder)
$ω habitat onboard nas-01 --tenant l1fe.ai
→ minted ed25519:nas-01 (tenant-scoped) → enrolled with substrate (oas:did:omega:host:nas-01) ✓ joined mesh; reachable via 100.84.21.42
$ω habitat hosts --tenant l1fe.ai
host arch mem cpu workloads uptime nas-01 x86_64 64GiB 16C archive.0 00:01:13 nas-02 x86_64 64GiB 16C archive.1 00:01:13 nas-03 x86_64 64GiB 16C archive.2 00:01:12 pi-shed-04 aarch64 4GiB 4C monitor.0 3d 14h
// rules
agent footprint
<5 MB static binary
agent auth
tenant-scoped Ed25519 keys
upgrade model
signed delta · auto-rollback
boundary
cryptographic — no cross-tenant scheduling
frontier capability
not available on Habitat (WASM only)
air-gap
full · use static peer lists + LAN overlay
Use it for

What Habitat
is best at.

Sensitive data that can't leave

HIPAA, FedRAMP-aligned, EU data residency, family photos. The data never crosses your perimeter; the substrate addresses it like it would any other brane.
DATA-LOCAL

On-prem first deployments

Companies that already own racks. Run the same Omega manifests as the cloud version, just pinned to your hardware.
ON-PREM

Edge & physical world

Phones in vehicles, sensors in factories, Pis in classrooms. The agent is small enough to ship with consumer hardware.
IOT

Hybrid bursts

Run baseline on Habitat, burst into Gaia / Biome when the queue grows. The brane address never changes.
HYBRID
← BiomeCapability profile — Frontier →