A Local Distributed Firebase Alternative

🪩 The Disco Party is MATA's distributed cloud — and SpaceDB is its database.

A local distributed Firebase alternative commits the write on the device in front of you, then lets other devices the same person owns catch up. Firebase does the opposite. The change rides to Google, then fans out. The app is only as alive as that round-trip.

SpaceDB is that alternative: local-first, CRDT-native, mesh-replicated, pure Rust. Encrypted replicas live on hardware the user already has. They converge when they reconnect. There is no per-user meter. The challenges of Firebase are the reason to want this. This page is the benefit: what "local" and "distributed" actually change once you stop treating a region as the database.

Why A Local Distributed Firebase Alternative Starts On The Device

Local means the write is finished before the radio is involved. The screen updates because the disk did, not because a data center acknowledged a packet. Distributed means there is more than one copy, and none of them is the boss. A phone, a laptop, and a box in the kitchen can all hold the same user's data. When two of them edit while apart, they merge. They do not ask Google which write won.

That is the shape of a distributed cloud: the cloud is the machines people already own. The Disco Party is MATA's name for it. A local distributed Firebase alternative is the database layer of that party. Firebase can still sit beside it for a workload that truly wants a single rented fan-out. It should not be the place a person's records live.

How A Local Distributed Firebase Alternative Behaves

Three benefits fall out of committing locally and replicating without a coordinator. They are the same three the SpaceDB write-up specifies. Here they are as the thing you feel.

A Local-First Distributed Database Writes Before The Network

A local distributed Firebase alternative never blocks correctness on a round-trip. Offline is the default. Connectivity adds sync. It does not add the right to exist. Reads are disk reads. Latency stops being a database product and becomes physics inside the machine. The NIST Zero Trust Architecture tells you to assume a device can be on its own. A local commit is that assumption with a storage engine.

A Local-First Distributed Database Merges The Copies

Two devices, one field, no coordinator: Firebase problems start here, because one replica — Google's — is allowed to pick a winner and drop the other write. A local distributed Firebase alternative uses conflict-free replicated data types. Diverged replicas converge on the same state when they meet, without dropping either write. Peer sync over iroh is the path. The merge is the database. Not every field wants the same strength. SpaceDB's per-field tiers — convergent, causal+, and strong — let a reaction counter and a balance share a schema.

The Keys Stay With The Person Who Owns The Rows

Every replica is encrypted with keys the user controls. The network operator does not get plaintext as a condition of carrying the bytes. Losing one device does not lose the data if another replica exists, or if peers hold ciphertext shards. That durability story is erasure coding. The Electronic Frontier Foundation is why "the vendor holds a copy for convenience" is not a neutral default. The three primitives are Trust, Security, Incentive: keys in your hand, a commit that does not wait on a region, and a peer paid to keep a shard. A local distributed Firebase alternative is custody you can point at.

What A Local Distributed Firebase Alternative Changes In The Product

The schema can stay familiar. The bill, the outage, and the subpoena change shape.

There Is No Per-User Meter On The Database

Firebase prices the path through Google. A local distributed Firebase alternative has no such meter. Hosting cost stops scaling with the number of people who open the app, because the open happens on their hardware. The Freedom Guide is built on that floor. Growth is not an invoice event.

Access Is A Grant, Not A Session That Sees Everything

Callers do not log into the database and then read the world. They present a capability: a signed grant, scoped in time and in what it may touch. Revocation is a dead grant, not a password reset at a vendor. Capability tokens are that pattern for the whole mesh. The Privacy Rights Clearinghouse is the catalog of what ambient, long-lived access becomes when the warehouse leaks.

SpaceDB Is The Local Distributed Firebase Alternative

The crate is SpaceDB. The page that already ranks for the comparison is the local-first database that replaces Firebase. Cards live on Remade with Rust. Use it where the data belongs to a person and the person has more than one device. Leave the rented primary for workloads that want an authoritative region. A local distributed Firebase alternative is not a slogan. It is a commit on hardware you can pick up.

The diagnosis is the challenges of Firebase when the network drops. The hub is SpaceDB. Files fetched by hash, not by a bucket URL, are content-addressed storage.