In detail.
The same idea, two currencies
Railway and BWEZE agree on how hosting should be billed: by what a service actually holds and uses, not by a box size chosen in advance. Railway meters memory and CPU by the second, at $10 per GB and $20 per vCPU for a month. BWEZE meters memory while a service runs, at 20 RWF per GiB-hour, and CPU time used, at 30 RWF per CPU-hour.
The differences are in how you pay and where it runs. Railway bills a plan fee (the Hobby plan’s $5 includes $5 of usage) and charges a post-paid card in dollars. BWEZE has no plan fee and takes francs from a prepaid wallet topped up with MoMo or IremboPay. When the wallet is empty, hosting gets 24 hours before it stops; there is no invoice afterwards.
A small stack on BWEZE:
| What | Amount | Rate | Cost |
|---|---|---|---|
| Web app, 512 MiB | 365 GiB-hoursat 20 RWF per GiB-hour | 20 RWF per GiB-hour | 7,300 RWF |
| Web app CPU, 5% on average | 36.5 CPU-hoursat 30 RWF per CPU-hour | 30 RWF per CPU-hour | 1,095 RWF |
| Worker, 256 MiB | 182.5 GiB-hoursat 20 RWF per GiB-hour | 20 RWF per GiB-hour | 3,650 RWF |
| Worker CPU, 3% on average | 21.9 CPU-hoursat 30 RWF per CPU-hour | 30 RWF per CPU-hour | 657 RWF |
| Postgres backend, 1 GiB | 730 GiB-hoursat 20 RWF per GiB-hour | 20 RWF per GiB-hour | 14,600 RWF |
| Postgres CPU, 10% on average | 73 CPU-hoursat 30 RWF per CPU-hour | 30 RWF per CPU-hour | 2,190 RWF |
| Postgres storage, 5 GiB | 5 GiB-monthsat 150 RWF per GiB-month | 150 RWF per GiB-month | 750 RWF |
| Before the free allowance | 30,242 RWF | ||
| Free allowance: 50 GiB-hours of app memory | -1,000 RWF | ||
| Free allowance: 5 CPU-hours of app CPU | -150 RWF | ||
| The month | 29,092 RWF | ||
Computed from BWEZE's published price list when this page was built. Memory is billed only while running; CPU only as used.
Where Railway is ahead
- Production today. Railway is generally available. BWEZE is in beta, with no SLA.
- Regions. Four regions on three continents. BWEZE will run in one data center in Kigali.
- Sleeping services. Railway can put an idle service to sleep and wake it on traffic. On BWEZE you stop a service yourself, and it costs nothing while stopped.
- Templates. Railway’s template library deploys common stacks in one click.
Moving from Railway to BWEZE
- Deploy the GitHub repository from the BWEZE dashboard; a Dockerfile, if there is one, is used as is.
- Copy each service’s variables and start command, and choose its type: web service, private service, worker or cron job.
- Move Postgres with
pg_dumpandpg_restoreinto a BWEZE backend. - Add your domains, then point DNS at BWEZE or move the domain to BWEZE Domains.