LinkedRecords – a graph-based Firebase replacement
Firebase replacement with server-sovereign data model; auth-as-schema is ambitious but execution unclear.

Firebase-killer with server-side auth, CRDT sync, and bring-your-own-backend model.
SaaS founders, enterprise teams prioritizing data sovereignty and compliance
Firebase · Supabase · Replicache
Firebase replacement with server-sovereign data model; auth-as-schema is ambitious but execution unclear.
BYOB BaaS with server-enforced auth—competes with Supabase, Firebase, and local-first architectures simultaneously.
Firebase-style BaaS but customers own their backend; authorization baked into data model.
Server-sovereign CRDT + authorization baked into data model, but no live demo or production evidence.
The neat twist is pushing real-time merging (CRDT/OT) into a server-authoritative BaaS while baking authorization into the data model itself — that’s a practical, non-obvious tradeoff compared to local-first systems. The README/landing shows a React hook SDK, OpenID Connect support, and an RDF-style query surface, which makes this feel like a deliberate platform for enterprise SaaS where auditability and data-jurisdiction matter. Worth watching if you need real-time collaboration but can’t accept vendor-controlled data or client-side auth.
This isn't another Firebase clone — it bakes authorization into the data model (you specify access when you create facts) and uses an RDF-style facts/triples API plus CRDT/OT for real-time merges. The demo hooks (useKeyValueAttributes) and OpenID Connect support make the client story feel thought-through, so this is worth a look if you need server‑sovereign, multi-app data sharing rather than a client-first offline story.