Skip to main content
Lark is wire-compatible with Firebase Realtime Database. If you have an existing Firebase RTDB app, you can point it at Lark with minimal changes.

​
What this means

The official Firebase SDKs can connect to Lark instead of Firebase. Your existing code (reads, writes, subscriptions, queries, transactions) works as-is. You don’t need to rewrite anything. Lark implements the same wire protocol that Firebase RTDB uses. When the Firebase SDK opens a WebSocket connection, it doesn’t know (or care) that it’s talking to Lark instead of Google’s servers. The messages are identical. The REST API is also fully compatible. If your backend hits Firebase’s /.json endpoints, change the hostname and it works with Lark.

​
Enabling Firebase compatibility

To use Firebase SDKs with Lark, toggle Allow Legacy Firebase in your project’s settings in the Lark dashboard. This enables the Firebase wire protocol on your project’s endpoint.

​
What’s different

Not much. Three things change:
  1. You point at larkdb.net instead of firebaseio.com for the connection URL.
  2. If you use Firebase Auth, you tell Lark your Firebase project ID so it can validate tokens.
  3. A few edge cases, documented in the compatibility notes.

​
What’s next

JavaScript SDK

Set up the Firebase JS SDK with Lark.

Android SDK

Set up the Firebase Android SDK with Lark.

iOS SDK

Set up the Firebase Apple SDK with Lark.

Migrating from Firebase

Step-by-step migration guide.