Show HN: LinkedRecords – a graph-based Firebase replacement
linkedrecords.comHi HN
I’m building LinkedRecords, an open-source backend-as-a-service designed for collaborative SaaS apps.
The core idea is simple:
Instead of collections and documents, LinkedRecords uses a graph-based triple store (facts: subject–predicate–object). Authorization is part of the data model itself — not a separate rules file. And real-time sync is built in from the start.
Why I built this
Most BaaS tools (Firebase, Supabase, Convex, etc.) are great — but they usually:
lock you into a hosted backend
separate auth rules from your actual data logic
use last-write-wins conflict resolution
make multi-tenant / server-sovereign setups hard
LinkedRecords takes a different approach:
Graph-native data model — flexible relationships without migrations
Authorization baked into queries — access control is enforced at the data layer
Real-time collaboration — conflict-aware merging instead of blind overwrites
Server-sovereign architecture — SaaS customers can choose where their data lives
Frontend-first usage — call the backend directly from your SPA
The goal is to make it easy to build collaborative tools (think Notion/Figma-style sync) while keeping control over hosting and data ownership.
It’s fully open source, and I’d love feedback.
Happy to answer any technical questions.
No comments yet.