Show HN: Graph-Based Firebase Alternative with Real-Time Sync
The article introduces LinkedRecords, a graph-based alternative to Firebase that allows for real-time synchronization. It provides a step-by-step guide for building a simple application using LinkedRecords with React and Vite. The tutorial covers setting up the backend, creating a project, and implementing a basic user interface without needing backend code.
- ▪LinkedRecords enables authentication, authorization, and data sharing between users without backend coding.
- ▪The tutorial guides users through creating a 'Hello World' application using React and Vite.
- ▪Users can start the LinkedRecords backend locally using Docker with a single command.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Linkedrecords |
| Canonical URL | https://linkedrecords.com/getting-started/ |
| Publication time | Sun, 17 May 2026 18:24:00 +0000 |
| Retrieval time | 2026-05-17T18:33:20.880Z |
| Last seen | 2026-05-17T18:33:20.880Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | ZEmgjpwP-ObI |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Getting StartedBuild your first LinkedRecords applicationBy the end of this tutorial, you will have a working application with authentication enabled, authorization out of the box, the ability to share data between users, and persistent storage - all without writing any backend code. Quick Start Start the LinkedRecords backend locally with a single command (requires Docker): [data-radix-scroll-area-viewport]{scrollbar-width:none;-ms-overflow-style:none;-webkit-overflow-scrolling:touch;}[data-radix-scroll-area-viewport]::-webkit-scrollbar{display:none}docker compose -p linkedrecords -f https://github.com/wolfoo2931/linkedrecords.git#main:docker-compose.yml up This docker-compose.yml is for local development only.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Linkedrecords.
Discussion
0 commentsMore from Linkedrecords
