In detail.
Two different shapes of hosting
Vercel runs your code as functions. An instance wakes for requests, and when the last request finishes it pauses and stops costing anything. That suits a front end with spiky traffic, and it is why Vercel bills memory per GB-hour of each instance’s lifetime and CPU only while code runs.
BWEZE runs your code as services: a container that stays up. That suits an API with steady traffic, a queue worker, a WebSocket server or anything built from a Dockerfile. Memory is billed while the service is up, at 20 RWF per GiB-hour, and CPU only as it is used, at 30 RWF per CPU-hour. Stop a service and it costs nothing.
Neither shape is better in general. A marketing site that sees a few hundred visits a day is cheap on functions. A backend that holds a database pool open all day is simpler as a service.
What a small app costs on BWEZE
A service with 256 MiB, up all month and mostly idle:
| What | Amount | Rate | Cost |
|---|---|---|---|
| Memory, 256 MiB for 730 hours | 182.5 GiB-hoursat 20 RWF per GiB-hour | 20 RWF per GiB-hour | 3,650 RWF |
| CPU, 2% of one CPU on average | 14.6 CPU-hoursat 30 RWF per CPU-hour | 30 RWF per CPU-hour | 438 RWF |
| Before the free allowance | 4,088 RWF | ||
| Free allowance: 50 GiB-hours of app memory | -1,000 RWF | ||
| Free allowance: 5 CPU-hours of app CPU | -150 RWF | ||
| The month | 2,938 RWF | ||
Computed from BWEZE's published price list when this page was built. Memory is billed only while running; CPU only as used.
We do not convert this to dollars here. The exchange rate moves, and a team topping up with mobile money pays the franc price. Vercel’s prices for the same month depend on the plan, the region and how many requests arrive, so take the numbers from its pricing page for your own traffic.
Where Vercel is ahead
- The edge. Static files and cached pages are served from a network Vercel says has 126 points of presence in 94 cities. BWEZE serves from Kigali.
- Next.js. Vercel builds Next.js, and features arrive there first.
- Regions. 19 compute regions, including Cape Town. BWEZE will have one.
- Track record. Vercel is generally available with a public status page. BWEZE is in beta, with no SLA and no status page yet.
Moving from Vercel to BWEZE
- Push the repository to GitHub, if it is not there, and deploy it from the BWEZE dashboard. A Next.js app builds automatically and runs as a Node server.
- Copy environment variables into the service’s settings. They are available at build and at runtime.
- If the app used Vercel’s Marketplace Postgres, create a BWEZE backend and restore a
pg_dumpinto it. - Add your domain to the service. BWEZE issues the certificate.
- Point DNS at BWEZE, or move the domain’s DNS to BWEZE Domains and keep everything in one account.
Sources
- Vercel pricing
- Vercel docs: Pro plan
- Vercel docs: Hobby plan
- Vercel terms of service
- Vercel docs: Regional pricing
- Vercel docs: Functions usage and pricing
- Vercel docs: Regions
- Vercel docs: Pro plan billing (payment methods)
- Vercel docs: Spend management
- Vercel docs: Postgres
- Vercel guide: Vercel Daemons
- Vercel docs: Instant Rollback
- Next.js docs: Self-hosting
- BWEZE price list (GET /v1/pricing)
- BWEZE docs: Deploy from Git