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

Server-sovereign BaaS where SaaS users control data location, authorization baked into schema.
SaaS founders building collaborative applications with data sovereignty requirements
Firebase · Supabase · Automerge
Firebase replacement with server-sovereign data model; auth-as-schema is ambitious but execution unclear.
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.
BYOB BaaS with server-enforced auth—competes with Supabase, Firebase, and local-first architectures simultaneously.
Graph-based BaaS rethinking authorization and data ownership against Firebase and Supabase.
Firebase-style BaaS but customers own their backend; authorization baked into data model.
Triplestore+CRDT beats local-first for server-enforced auth, but positioning vs. Convex and Supabase unclear.