Switch from Firebase

Auth, files and SQL equivalents — not a Firestore import

Kuunda does not import Firestore or Realtime Database. You recreate the model in PostgreSQL, then Auth and Storage in the console. @kuunda/kuunda-js SDK.

Email / OAuth Auth in the console — not a Firebase Auth dump
S3-compatible Storage instead of Cloud Storage
Postgres + REST API instead of Firestore

Relational model

Firestore documents map to SQL tables and RLS policies. This work is manual: the import assistant does not read a Firestore export.

Latency

West African users: fewer round-trips to an extra-African region.

Readable pricing

Monthly FCFA plans, published on the pricing page — not per-read Firestore billing.

Kuunda stack: PostgreSQL per project, REST API, authentication, Storage, Realtime and Edge Functions — data hosted in Abidjan. On top of that: Kuunda Git (hosted Git) and Kuunda Sage (data analyst).

Guide: what Kuunda imports (and what it does not)

Included with every project

Beyond the stack, two Kuunda tools follow the project from the first commit to production.

Kuunda Git

Git repositories hosted in Africa: push, scoped tokens and a deploy on every push

Read the documentation

Kuunda Sage

AI analyst for your database: plain-language questions, read-only answers