In detail.
A backend, or a backend and everything around it
Supabase is a backend: Postgres per project, with auth, file storage, realtime and Edge Functions around it. Your front end and any long-running server live somewhere else, and phone sign-in needs an SMS provider you contract separately.
A BWEZE backend project is also Postgres with auth, storage, realtime and pgvector. The difference is the rest of the account: the app that uses the backend deploys next to it from GitHub, sign-in codes go out through BWEZE’s own SMS API, and the domain’s DNS lives there too. One wallet in francs pays for all of it.
What a backend costs on BWEZE
Backends are billed like apps: memory while running, at 20 RWF per GiB-hour, CPU as used, and storage per GiB-month. A backend with 1 GiB, light load, 8 GiB of data, and 1,000 sign-in codes:
| What | Amount | Rate | Cost |
|---|---|---|---|
| Backend memory, 1 GiB for 730 hours | 730 GiB-hoursat 20 RWF per GiB-hour | 20 RWF per GiB-hour | 14,600 RWF |
| Backend CPU, 10% on average | 73 CPU-hoursat 30 RWF per CPU-hour | 30 RWF per CPU-hour | 2,190 RWF |
| Data and files, 8 GiB | 8 GiB-monthsat 150 RWF per GiB-month | 150 RWF per GiB-month | 1,200 RWF |
| Sign-in codes, 1,000 one-segment SMS | 1,000 segmentsat 15 RWF per segment | 15 RWF per segment | 15,000 RWF |
| The month | 32,990 RWF | ||
Computed from BWEZE's published price list when this page was built. Memory is billed only while running; CPU only as used.
The free monthly allowance covers app hosting, not backends, so a backend is paid from the first hour. A stopped backend keeps its data and pays only for storage.
Where Supabase is ahead
- Maturity. Supabase is generally available. BWEZE backends are in beta.
- Backups. Daily backups on Pro and point-in-time recovery as an add-on. BWEZE’s backup job is not running yet, and until it is, keep your own
pg_dumpof anything you cannot lose. - Ecosystem. Client libraries for many languages, Edge Functions in 15 regions, database branching and a large community.
- Free tier. Two free projects for prototypes. BWEZE’s free allowance does not cover backends.
Moving data between them
Both are Postgres, so pg_dump and pg_restore move tables and data either way. Auth users, storage objects and functions need their own migration, and the code that calls the backend needs testing against BWEZE before you switch.