Switch from Supabase

Same Postgres, Auth and Storage — data in Abidjan

Console assistant: Postgres URI + schema.sql / data.sql, then Import auth.users and Storage buttons. Docs guide /import/supabase.

Assistant: BaaS export (public schema) or PostgreSQL + dump
Import auth.users (up to 2,000) and Storage (50 buckets, 2,000 files, 50 MB/file)
@kuunda/kuunda-js SDK, API close to supabase-js

SQL rewritten to the tenant

The public schema becomes proj_{uuid32hex}. RLS, views and triggers come from the dump; the assistant rewrites incompatible extensions when planned.

Real assistant limits

SQL file ~20 MB, 500 inventoried tables. Edge Functions, Vault, pg_cron, webhooks and SMTP are not imported: redeploy / reconfigure manually.

Region

Kuunda project data hosted in Abidjan, not on Supabase infra.

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).

Supabase migration guide

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