What if the internet stack was re-architected from first principles?
The Grid isn't cheaper AWS. It's a different shape. Apps don't have backends. Users own their data. Every payment is a signed receipt, settled per epoch in stablecoin, verifiable on-chain. Operators are infrastructure providers, not crypto miners. One DID, one protocol, many front-ends.
Five categories of centralized infrastructure, replaced by protocol primitives.
The shape of the stack.
You own your data
Your bytes (L1), your universal metadata (L2), and aggregate signals (L4) live in your DID-rooted vault. Apps store their proprietary fields (L3) in their own namespace — you grant them access via capability tokens, you can revoke any time. Apps don't hold copies of your address book.
See the data model →Apps don't have backends
On The Grid, you don't write CRUD APIs. You define schemas, capability rules, and event triggers — the protocol does the rest. Side effects (email, payments, validations) are WASM functions running in def:xsr triggered by data events. No HTTP API layer. No user database. No auth implementation. No payments integration.
How to build →Receipts, not invoices
Every request anchors a signed receipt to a block. Every epoch (~30 min) closes with deterministic settlement — two honest nodes running the same code produce byte-identical results. No vendor estimates, no monthly reconciliations, no surprise charges. Verifiable byte-for-byte forever.
See pricing →One DID, many front-ends
Your DID is your account on The Grid — works on any app, on any front-end, forever. gridprotocol.io is one front-end of many; anyone can build their own using the SDK. Your chain account is a first-class primitive at the protocol layer, regardless of which UI created it.
Build a front-end →Operators run real workloads
The Grid's operators are small ISPs, colos, and edge networks competing in a market for actual demand: CDN traffic, GPU jobs, storage reads. NPV-weighted placement rewards rare topology. Stake backs reputation. Every payout settles in stablecoin per epoch. This isn't mining.
Operate a node →Verifiable computation
def:tvo aggregates operator attestations on-chain. Sanctuary (Demo 10) wraps workloads in TEEs with hardware attestation. Veil (Demo 11) returns ZK proofs alongside results. Cryptographic certainty that the code ran correctly — for regulated finance, healthcare, AI safety, and the agentic era.
Trust & verifiability →Asked + answered, plainly.
Isn't this just blockchain?
No. Most "blockchain" platforms put a token on-chain and keep the actual product data in a normal database. The Grid does the opposite — receipts, capabilities, reputation, and settlement live on-chain, while user data lives in DID-rooted vaults you control. Chain primitives serve a stack rebuild, not a token launch.
Aren't you just decentralized AWS?
AWS is one piece of what The Grid replaces. The full picture: AWS + your CRUD layer + your auth + your payments + your CRM + your analytics. The Grid replaces the whole stack with protocol primitives. The cost story is real, but it's the smallest part of the pitch.
How is this different from web3?
Web3 platforms generally optimize for speculative tokens and DEX trading. The Grid optimizes for real workloads with real settlement. GRID is the network's stake/governance token; users and operators settle in stablecoin. We don't pitch as crypto — we pitch as infrastructure.
Is the Foundation in control?
No. The Foundation operates gridprotocol.io as a reference front-end. Protocol changes go through on-chain governance — validators and token-holders vote. v1-beta has Foundation training-wheel operators; v2 is permissionless. Code is MIT, auditable, forkable. Decentralization is a gradient and we're honest about where on it we are.