Grid Infra · the technical layer

Build on infrastructure you don't rent.

Compute, storage, identity, and delivery as a protocol. Operators keep 100% of fees, you deploy in minutes — no servers, no DNS, no accounts to wire up.

$ grid init · deploy in minutes · 0% take rate

The four-layer stack

One protocol, four layers deep.

The Grid is a full stack, not a single service. Each layer builds on the one below it — from raw operator resources all the way up to the browser users open.

01

Decentralized Resources

Compute, storage, identity, and KMS served directly from operator nodes — a global pool of capacity instead of a handful of regions you rent.

02

Personal Data Vaults + Grid Auth

User data lives in a vault the user owns. Apps never hold it outright — they request revocable capability tokens scoped to exactly what they need.

03

Grid Programs

Applications compile to WASM and run as portable Grid Programs — no servers to provision, no DNS to configure, no per-app account sprawl.

04

Grid Browser

A forked Chromium client speaking HTTP/3 that resolves Grid Programs and assembles them on the device — the runtime users actually touch.

Resources → Vaults & Auth → Programs → Browser

14 services planned · 4 live by Q3 2026

The services you'd reach for, as a protocol.

Delivery, storage, identity, and hosting ship first. Compute and key management follow — every service served by the operator network, with no protocol take rate.

Live Q3 2026

CDN / Delivery

Content and asset delivery routed across operator nodes, close to the request.

Live Q3 2026

Object & Archival Storage

Durable object and archival storage — shipping as the Grid “Data” service.

Live Q3 2026

Identity / Grid Auth

Capability-based auth: scoped, revocable tokens issued against a user's vault.

Live Q3 2026

Web / Hosting

Host Grid Programs and static sites directly on the network — no origin to manage.

Coming

Edge Compute

Run WASM workloads at the edge of the operator network, near the data and the user.

Coming

KMS

Key management and cryptographic operations as a first-class network primitive.

Three sides, one network

Value flows peer-to-peer — no middleman cut.

The Grid connects the people who provide capacity, the people who build on it, and the people who use it. Nothing is skimmed in between.

Operators provide

Run a node on hardware you own and serve real capacity to the network. Operators keep 100% of the fees they earn — there's no protocol cut in the middle.

Developers build

Ship WASM Grid Programs that self-assemble in the browser. No servers to provision, no DNS to wire up, no per-app accounts to stand up — just deploy.

Users own

Every user's data lives in a Personal Data Vault. Apps operate on revocable capability tokens, so access can be granted — and pulled back — in seconds.

Operators Developers Users

Why Grid

The only layer that checks every box.

Hyperscalers give you the full stack — but you don't own the data and you pay their margin. Decentralized peers give you ownership, one resource at a time. The Grid does both.

CapabilityThe GridHyperscalersDecentralized peers
You own your data
0% protocol take rate
Full stack — compute + storage + identity + delivery + browser
Anyone can operate
Apps assemble themselves

Quickstart

Two commands to a live Grid Program.

Scaffold a project, compile to WASM, and deploy it to the network. No origin server to stand up, no DNS records to point, no dashboard to click through.

bash — my-app
# scaffold a new Grid Program
$ grid init my-app
✓ created my-app/ · WASM target ready

# compile + ship to the network
$ cd my-app && grid deploy
⠿ building wasm · publishing to operators…
✓ live my-app.grid · 0 servers · 0 DNS · 0% take rate

Proof it runs

Not a whitepaper — a network.

The Grid is live and under test today. These are the real numbers behind the protocol you'd build on.

0

Validators online

0

Countries live

0+

Rust crates

0

Consensus tests

0 TB

Storage live

Roadmap

From closed beta to mainnet.

A deliberate path: ship the core services to builders, harden with a security audit, then open the full stack to everyone.

Q3 2026

Closed beta

The first four services go live — Delivery, Data, Identity, and Hosting — to a closed set of builders.

Q4 2026

Services 5–9 + security audit

Edge Compute, KMS, and the next wave of services land, alongside a full third-party security audit.

H1 2027

Grid Browser + mainnet

Grid Browser launches to everyone and the network reaches mainnet — the full stack, end to end.

Build on The Grid. Own the stack.

Compute, storage, identity, and delivery as a protocol — deploy in minutes and keep the network working for you, not the other way around.