No Egress Bill — The Economics Of A Distributed Cloud

🪩 The Disco Party is MATA's distributed cloud.

An egress bill is the tax for leaving. Centralized cloud stores your bytes cheaply enough to feel friendly, then invoices you when those bytes walk out — to a user, to another vendor, to your own laptop. Distributed cloud economics delete that line item. Data already lives near the people who own it. Peers fetch from peers. When someone contributes uplink, the network pays them. There is no region boundary to "egress" across, so there is no egress bill to print.

That is not a pricing gimmick. It is the shape of the mesh. What Is A Distributed Cloud is the architecture. This article is the invoice you stop receiving. The Disco Party is the market that replaces it.

Why The Egress Bill Exists — And Why Distributed Cloud Economics Refuse It

Hyperscalers lose money if you treat S3 as a disk and CloudFront as a courtesy. The egress bill exists to make leaving expensive and staying habitual. Move a dataset to another cloud and you fund the old one as you go. Serve users from the region you stored in and you still pay to leave the building. Distributed cloud economics start from the opposite assumption: the building is the users. Bytes that move from one home to another are the product working, not a premium SKU.

Incentive is the Digital Freedom primitive that maps to payouts. An egress bill is Incentive inverted — the platform is the only party that gets paid for motion. Trust is identity so contributors can receive. Security is encryption so motion is not a plaintext leak. The Federal Trade Commission has been staring at cloud concentration for years. The egress bill is one of the levers that concentration uses. A distributed cloud that pays the opposite direction is a market structure, not a coupon.

The Electronic Frontier Foundation treats expensive exit as a speech issue: if leaving is priced as a luxury, publishing is rented. Distributed cloud economics keep publishing on hardware you already bought.

How Distributed Cloud Economics Replace The Egress Bill

SpaceDB stores encrypted entries on devices. Transport is iroh. Settlement pays the hop. You do not "download from the cloud" and trigger a meter. You gossip with a peer. Peer-to-peer device sync is the everyday version. This page is the spreadsheet version.

Ingress Was Always Cheap — The Egress Bill Is The Trap

Vendors price ingest like a welcome gift. The egress bill is the door that locks behind you. Distributed cloud economics do not offer a gift. They offer a seam: you write locally, you sync when you want, you pay contributors when their uplink did work. No surprise line item at the end of the month because a product launch was popular.

Contributors Get The Money The Egress Bill Used To Take

Idle CPU, storage, and bandwidth earn. That is the same Incentive story as idle devices on the distributed cloud, settled through SpaceDB's Settlement seam and Iron Bank. The IETF HTTP semantics already treat a response as something a server chose to send. Distributed cloud economics treat that send as work a peer can be paid for, not a violation of a region contract.

Local-First Means Most Bytes Never Meet An Egress Bill

SpaceDB commits locally. Reads hit disk. A popular object is a CID many homes already hold. Content-addressed fetch asks the nearest peer, not a bucket in Virginia. The NIST Zero Trust Architecture does not require a metered perimeter. It requires a verified request. Capability tokens are that verify. The egress bill is a perimeter tax and has no place in the model.

Distributed Cloud Economics Are How The Disco Stays Honest

If the only way to grow is to extract more egress, the product will fight its users. If growth pays more contributors, the product will recruit them. Digital Freedom is Trust, Security, and Incentive — identity, encryption, payouts. The Freedom Guide is how a person joins the market. What Is Digital Freedom is the why. Remade With Rust is the stack that can run on the machines you already own.

An Egress Bill Is Also A Privacy Bill

Meters require logs. Logs become a map of who fetched what. The Privacy Rights Clearinghouse is a museum of those maps after they leak. Distributed cloud economics meter settlement on sealed work, not on a vendor's access log of your reading habits. The NIST Secure Software Development Framework wants less sensitive residue in the system. Killing the egress bill kills a residue class.

Predictable Cost Is A Feature Users Can Feel

Sign in with Sovereign ID already deleted the MAU fee. Distributed cloud economics delete the egress bill next. Two meters gone. What remains is payouts to people who contributed. That is a cost curve a small business can draw on a napkin. The Learn index and the home page are the rest of the napkin.

Remade Primitives, Disco Party, Digital Freedom

SpaceDB, iroh, mID, and Settlement are Remade-With-Rust primitives. They become a disco party when distributed cloud economics pay the room instead of taxing the exit. They become Digital Freedom when Trust, Security, and Incentive run without an egress bill. Start at the Disco Party. Keep the bytes. Pay the peers. Stop funding the door.

Who gets paid instead of the region is idle devices. What you fetch without a bucket invoice is content-addressed storage. The definition this economics sits on is what a distributed cloud is.