# BWEZE vs Railway: usage-priced hosting, in RWF or USD

> Both bill memory and CPU by what runs. Railway charges in USD by card from four regions; BWEZE charges in RWF from mobile money and adds SMS.

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

Railway is the closest thing to BWEZE on this list. Both bill memory and CPU for what a service uses instead of renting instance sizes, both deploy from GitHub or a Dockerfile, and both sell domains. Railway charges in dollars to a post-paid card from four regions in the US, Europe and Asia. BWEZE charges in francs from a prepaid wallet topped up with mobile money, and adds an SMS API to Rwandan phones.

Railway facts checked 17 November 2026.

## Choose BWEZE if

- You pay in RWF with mobile money and want a prepaid wallet, not a post-paid card.
- Your users are in Rwanda; Railway's four regions are in the US, the Netherlands and Singapore.
- You send SMS to Rwandan numbers and want it on the same bill as hosting.
- You want no monthly plan fee at all, only usage.

## Choose Railway if

- You need a platform in production today, with a public track record. BWEZE is in beta.
- Your users are in North America, Europe or Southeast Asia.
- You want services that sleep on their own when idle (Railway's opt-in Serverless setting).
- You want Railway's templates and its project canvas.

## Side by side

| | BWEZE | Railway |
| --- | --- | --- |
| **Billing** | | |
| Currency | Rwandan francs (RWF) | US dollars |
| How you pay | Mobile money (MoMo) or IremboPay, into a prepaid wallet | Credit card, post-paid |
| Monthly fee | None | Free $0 with $1 of credit; Hobby $5 with $5 of usage; Pro $20 with $20 of usage |
| Memory | 20 RWF per GiB-hour, while a service runs | $10 per GB a month, billed by the second |
| CPU | 30 RWF per CPU-hour, for CPU time used | $20 per vCPU a month, billed by the second |
| Storage | 150 RWF per GiB-month (backends) | $0.15 per GB a month (volumes) |
| Outbound bandwidth | Not metered on today's price list | $0.05 per GB |
| Builds | Not metered on today's price list | Free |
| Spend limit | Prepaid: stops at zero, never in debt (24 hours to top up hosting) | A hard limit you set shuts workloads down |
| **Platform** | | |
| Where it runs | Kigali, one data center, when the beta opens | California, Virginia, Amsterdam, Singapore; none in Africa |
| Deploy from Git | GitHub | GitHub |
| Dockerfile | Yes | Yes |
| Preview per pull request | For web services | PR environments |
| Rollbacks | Yes | One click; images kept 72 hours on Hobby, 120 on Pro |
| Sleep when idle | A stopped service costs nothing; no automatic sleep | Opt-in Serverless: sleeps 5 to 10 minutes after the last outbound traffic |
| **Beyond hosting** | | |
| Postgres | Backend projects: Postgres with auth, storage, realtime and pgvector | A Postgres template, billed as usage |
| SMS API | To Rwandan numbers, 15 RWF per segment | No |
| Domains and DNS | DNS and domains in your name | Railway Domains, with Railway-managed DNS |
| Status | Beta, opening to the waitlist; no SLA yet | Generally available |

## 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:

**A web app, a worker and Postgres on BWEZE, one month**

| What | Amount | Rate | Cost |
| --- | --- | --- | --- |
| Web app, 512 MiB | 365 GiB-hours | 20 RWF per GiB-hour | 7,300 RWF |
| Web app CPU, 5% on average | 36.5 CPU-hours | 30 RWF per CPU-hour | 1,095 RWF |
| Worker, 256 MiB | 182.5 GiB-hours | 20 RWF per GiB-hour | 3,650 RWF |
| Worker CPU, 3% on average | 21.9 CPU-hours | 30 RWF per CPU-hour | 657 RWF |
| Postgres backend, 1 GiB | 730 GiB-hours | 20 RWF per GiB-hour | 14,600 RWF |
| Postgres CPU, 10% on average | 73 CPU-hours | 30 RWF per CPU-hour | 2,190 RWF |
| Postgres storage, 5 GiB | 5 GiB-months | 150 RWF per GiB-month | 750 RWF |
| **Before the allowance** | | | **30,242 RWF** |
| Free allowance: app memory | 50 GiB-hours | | -1,000 RWF |
| Free allowance: app CPU | 5 CPU-hours | | -150 RWF |
| **Month** | | | **29,092 RWF** |

## 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

1. Deploy the GitHub repository from the BWEZE dashboard; a Dockerfile, if there is one, is used as is.
2. Copy each service's variables and start command, and choose its type: web service, private service, worker or cron job.
3. Move Postgres with `pg_dump` and `pg_restore` into a BWEZE backend.
4. Add your domains, then point DNS at BWEZE or move the domain to BWEZE Domains.
## Questions

### Is BWEZE's memory price close to Railway's?

Both bill memory for what runs. Railway lists $10 per GB a month; BWEZE lists 20 RWF per GiB-hour, which is 20 RWF times 730 hours for a GiB running a whole month. Which is cheaper depends on the exchange rate on the day you pay, so we leave the conversion to you.

### Does Railway accept mobile money?

Not that we found. Railway's docs say it accepts credit cards for plan subscriptions and now requires a post-paid card; Enterprise customers can get custom invoicing.

### Can I keep my app on Railway and send SMS through BWEZE?

Yes. The SMS API is a plain HTTPS call with a secret key, so it works from any host. Each send is 15 RWF per segment from your BWEZE wallet.

## Sources

- [Railway pricing](https://railway.com/pricing)
- [Railway docs: Plans](https://docs.railway.com/pricing/plans)
- [Railway docs: Free trial](https://docs.railway.com/pricing/free-trial)
- [Railway docs: Pricing FAQs](https://docs.railway.com/pricing/faqs)
- [Railway docs: Cost control](https://docs.railway.com/pricing/cost-control)
- [Railway docs: Regions](https://docs.railway.com/deployments/regions)
- [Railway docs: Serverless](https://docs.railway.com/deployments/serverless)
- [Railway docs: Environments](https://docs.railway.com/environments)
- [Railway docs: Railway Domains](https://docs.railway.com/networking/domains/railway-domains)
- [BWEZE price list (GET /v1/pricing)](https://api.bweze.com/v1/pricing)
- [BWEZE docs: Messaging](https://docs.bweze.com/docs/messaging)
