# BWEZE vs Render: services and Postgres, priced two ways

> Render rents instances by the month in USD, from five regions. BWEZE bills memory while running and CPU as used, in RWF, with SMS and DNS included.

Source: https://bweze.com/compare/render/ · Updated 2026-11-17

Render and BWEZE host the same kinds of things, web services, workers, cron jobs and Postgres, from a Git push or a Dockerfile. Render prices fixed instance sizes in dollars from five regions in the US, Europe and Asia. BWEZE prices what a service holds and uses, in francs paid with mobile money, and adds SMS and DNS to the same bill.

Render facts checked 17 November 2026.

## Choose BWEZE if

- You want to pay for memory while a service runs and CPU only as it is used, not for a fixed instance size.
- You pay in RWF with mobile money, and want a prepaid ceiling instead of a card bill.
- Your users are in Rwanda; none of Render's five regions is in Africa.
- You also send SMS or run your domain's DNS, and want one account for all of it.

## Choose Render if

- You need production today, with managed Postgres point-in-time recovery, read replicas and high availability.
- You need autoscaling, or full-stack preview environments for every pull request.
- Your users are in the US, Europe or Southeast Asia, where Render's regions are.
- Your team deploys from GitLab or Bitbucket as well as GitHub.

## Side by side

| | BWEZE | Render |
| --- | --- | --- |
| **Billing** | | |
| Currency | Rwandan francs (RWF) | US dollars |
| How you pay | Mobile money (MoMo) or IremboPay, into a prepaid wallet | Credit or debit card, through Stripe |
| Monthly fee | None | Hobby $0 plus compute; Pro $25 per workspace plus compute, unlimited seats |
| Compute | 20 RWF per GiB-hour while running, plus 30 RWF per CPU-hour used | Fixed instance sizes by the month, prorated by the second: from $7 for 0.5 CPU and 512 MB |
| Free usage | 50 GiB-hours of memory and 5 CPU-hours a month, after verifying a Rwandan mobile number | Free web services sleep after 15 idle minutes; 750 instance hours a month |
| Outbound bandwidth | Not metered on today's price list | 5 GB (Hobby) or 25 GB (Pro) included, then $0.15 per GB |
| Build minutes | Not metered on today's price list | 500 (Hobby) or 1,000 (Pro) a month, then $5 per 1,000 |
| Spend limit | Prepaid: stops at zero, never in debt (24 hours to top up hosting) | A spend limit for build minutes; no workspace-wide cap found |
| **Platform** | | |
| Where it runs | Kigali, one data center, when the beta opens | Oregon, Ohio, Virginia, Frankfurt, Singapore; none in Africa |
| Deploy from Git | GitHub | GitHub, GitLab, Bitbucket |
| Dockerfile | Yes | Yes |
| Web services | Yes | Yes |
| Preview per pull request | For web services | Per service on all plans; full-stack environments on Pro |
| Rollbacks | Yes | Instant; 5 builds kept on Hobby, 15 on Pro |
| Pay nothing while stopped | Yes | Free web services spin down; paid instances bill while they exist |
| **Postgres** | | |
| Managed Postgres | Backend projects: Postgres with auth, storage, realtime and pgvector | From $6 a month; free databases expire after 30 days |
| Storage | 150 RWF per GiB-month | $0.30 per GB a month |
| Backups and point-in-time recovery | Not running yet | Point-in-time recovery: 3 days on Hobby, 7 on Pro |
| **Beyond hosting** | | |
| SMS API | To Rwandan numbers, 15 RWF per segment | No |
| DNS and domains | DNS and domains in your name | Use your own DNS provider |
| Status | Beta, opening to the waitlist; no SLA yet | Generally available |

## Instances or meters

Render sells instances. You choose a size, 0.5 CPU and 512 MB for $7 a month at the bottom, and pay for it by the second while it exists, whatever the CPU does. That is predictable: the price of a month is on the pricing page.

BWEZE sells meters. Memory is billed while a service runs, at the size you set, at 20 RWF per GiB-hour. CPU is billed for the time actually used, at 30 RWF per CPU-hour. A service that idles most of the day pays mostly for its memory. Here is an API with 512 MiB that averages a tenth of a CPU:

**An API with 512 MiB on BWEZE, up all month at 10% CPU**

| What | Amount | Rate | Cost |
| --- | --- | --- | --- |
| Memory, 512 MiB for 730 hours | 365 GiB-hours | 20 RWF per GiB-hour | 7,300 RWF |
| CPU, 10% of one CPU on average | 73 CPU-hours | 30 RWF per CPU-hour | 2,190 RWF |
| **Before the allowance** | | | **9,490 RWF** |
| Free allowance: app memory | 50 GiB-hours | | -1,000 RWF |
| Free allowance: app CPU | 5 CPU-hours | | -150 RWF |
| **Month** | | | **8,340 RWF** |

## Where Render is ahead

- **Production Postgres.** Render's managed Postgres has point-in-time recovery, read replicas and high availability today. BWEZE backends do not have backups running yet, and we will not call them production-ready for data you cannot lose until they do.
- **Autoscaling and preview environments.** Render scales services on Pro and can spin up a whole stack per pull request. BWEZE previews web services one at a time.
- **Regions and maturity.** Five regions, generally available. BWEZE will run in one data center in Kigali, in beta.
- **Git providers.** GitLab and Bitbucket as well as GitHub.

## Moving from Render to BWEZE

1. Deploy the same repository from the BWEZE dashboard. If Render built it from a Dockerfile, BWEZE uses the same file.
2. Recreate each service with its type: web service, private service, background worker or cron job. Copy its environment variables and start command.
3. Move Postgres with `pg_dump` and `pg_restore` into a BWEZE backend, and update the connection string.
4. Add your domains, then point DNS at BWEZE or move it to BWEZE Domains.
## Questions

### Is BWEZE cheaper than Render?

It depends on the shape of the service. Render charges a fixed price per instance size whether the CPU is busy or idle. BWEZE charges for configured memory while the service runs and for CPU time actually used, so a mostly idle service pays little for CPU. Price your own service from both lists; we do not convert currencies because the rate moves.

### Does Render have a region in Africa?

No. Render's regions are Oregon, Ohio and Virginia in the US, Frankfurt and Singapore, and an existing service or database cannot change region.

### Can I move a Render Postgres database to BWEZE?

Yes. Both are standard Postgres. Take a dump with pg_dump from Render and restore it with pg_restore into a BWEZE backend, then change the connection string in your services.

## Sources

- [Render pricing](https://render.com/pricing)
- [Render docs: Free instances](https://render.com/docs/free)
- [Render docs: Regions](https://render.com/docs/regions)
- [Render docs: Outbound bandwidth](https://render.com/docs/outbound-bandwidth)
- [Render docs: Build pipeline](https://render.com/docs/build-pipeline)
- [Render docs: Preview environments](https://render.com/docs/preview-environments)
- [Render docs: Docker](https://render.com/docs/docker)
- [Render docs: Custom domains](https://render.com/docs/custom-domains)
- [BWEZE price list (GET /v1/pricing)](https://api.bweze.com/v1/pricing)
- [BWEZE docs: Deploy from Git](https://docs.bweze.com/docs/deploy)
