# Lovable — How we moved our frontend off Firestore and built Lovable Realtime

- Company: Lovable (lovable.dev)
- Announced: 2026-11-09T11:30:00+00:00
- Category: infrastructure-release
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://lovable.dev/blog/lovable-realtime-service
- Record: https://forck.live/items/33385-how-we-moved-our-frontend-off-firestore-and-built-lovable-realtime
- Subject: Lovable / AI app builder

Lovable built its own realtime service, Lovable Realtime, to move its frontend off direct Firestore listeners and put authorization and payload shaping in its Go backend. The company says the browser previously received whole Firestore documents, so adding a database field could expose it, and permissions had to be kept in sync between Firestore rules and the Go API. Firestore rules also could only query Firebase data, which blocked authorization updates for large groups such as enterprise SCIM-synced engineering groups whose data lives in Spanner. Lovable says it built the core in 40 hands-on working days and rolled it out to every user without a single user-facing incident. The service handles peaks of over 2 million concurrent subscriptions and delivers around 2.6 billion data and patch frames per month. It is a dedicated WebSocket service with one connection per tab and all subscriptions multiplexed over it, and it works with the existing Firestore and Spanner stores rather than requiring a new primary database.

## Evidence

Verbatim from https://lovable.dev/blog/lovable-realtime-service:

> Adding a field to a database document shouldn’t also be a decision about what users can see in their browsers.
> 
> With our frontend listening directly to Firestore, it could be. The browser received whole documents, permissions had to stay synchronized between Firestore rules and our Go backend, and features that needed data from other databases ran into those boundaries. We needed the backend to decide what each user received and keep that decision up to date as both the data and their permissions changed. At millions of live subscriptions, we also needed to do it efficiently.
> 
> That led us to build Lovable Realtime, our own realtime service.
> 
> I built the core in 40 hands-on working days, and we rolled it out to every user without a single user-facing incident. The service handles peaks of over 2 million concurrent subscriptions and delivers around 2.6 billion data and patch frames per month.
> 
> We needed three things together: support for our existing databases, backend-shaped payloads, and reactive authorization. The alternatives either required changing our database stack or left substantial parts of that framework for us to build.

---

Record: https://forck.live/items/33385-how-we-moved-our-frontend-off-firestore-and-built-lovable-realtime
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
