In detail.
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:
| What | Amount | Rate | Cost |
|---|---|---|---|
| Memory, 512 MiB for 730 hours | 365 GiB-hoursat 20 RWF per GiB-hour | 20 RWF per GiB-hour | 7,300 RWF |
| CPU, 10% of one CPU on average | 73 CPU-hoursat 30 RWF per CPU-hour | 30 RWF per CPU-hour | 2,190 RWF |
| Before the free allowance | 9,490 RWF | ||
| Free allowance: 50 GiB-hours of app memory | -1,000 RWF | ||
| Free allowance: 5 CPU-hours of app CPU | -150 RWF | ||
| The month | 8,340 RWF | ||
Computed from BWEZE's published price list when this page was built. Memory is billed only while running; CPU only as used.
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
- Deploy the same repository from the BWEZE dashboard. If Render built it from a Dockerfile, BWEZE uses the same file.
- Recreate each service with its type: web service, private service, background worker or cron job. Copy its environment variables and start command.
- Move Postgres with
pg_dumpandpg_restoreinto a BWEZE backend, and update the connection string. - Add your domains, then point DNS at BWEZE or move it to BWEZE Domains.