1. BWEZE
  2. Blog
  3. Costs

Costs · 3 min read

What it costs to run a production app on BWEZE

Four real workloads priced line by line from the published price list, from a small app to a startup's whole stack, and the three changes that cut a bill most.

Hosting prices are easy to read and hard to apply. A rate like 20 RWF per GiB-hour tells you little until you know how much memory your app holds and for how long. So here are four workloads priced line by line. Every number on this page is computed from BWEZE’s published price list when the page is built, so it stays right if a price changes.

Two rules decide almost every bill:

  • Memory is billed while a service runs, at the size you configured. It is 20 RWF per GiB-hour. A stopped service holds no memory and costs nothing.
  • CPU is billed for what is used, not for what is allowed. It is 30 RWF per CPU-hour. An app that sits at 2% of a CPU pays for 2%.

A small app

A marketing site, an internal tool or an early product: one web service with 256 MiB, up all month, mostly idle.

Cost exampleA small app, running all month
WhatAmountRateCost
Web app memory, 256 MiB for 730 hours182.5 GiB-hoursat 20 RWF per GiB-hour20 RWF per GiB-hour3,650 RWF
Web app CPU, 2% of one CPU on average14.6 CPU-hoursat 30 RWF per CPU-hour30 RWF per CPU-hour438 RWF
Before the free allowance4,088 RWF
Free allowance: 50 GiB-hours of app memory-1,000 RWF
Free allowance: 5 CPU-hours of app CPU-150 RWF
The month2,938 RWF

Computed from BWEZE's published price list when this page was built. Memory is billed only while running; CPU only as used.

The free allowance takes off 50 GiB-hours of memory and 5 CPU-hours of CPU each month, once the workspace owner has verified a Rwandan mobile number. It applies to app usage only, not to backends, SMS or domains.

A startup’s production stack

Something closer to a real product: a web app and an API at 512 MiB each, a queue worker, a Postgres backend with 1 GiB of memory and 10 GiB of data, and 2,000 sign-in codes by SMS.

Cost exampleA startup's production stack, one month
WhatAmountRateCost
Web app, 512 MiB365 GiB-hoursat 20 RWF per GiB-hour20 RWF per GiB-hour7,300 RWF
Web app CPU, 5% on average36.5 CPU-hoursat 30 RWF per CPU-hour30 RWF per CPU-hour1,095 RWF
API, 512 MiB365 GiB-hoursat 20 RWF per GiB-hour20 RWF per GiB-hour7,300 RWF
API CPU, 10% on average73 CPU-hoursat 30 RWF per CPU-hour30 RWF per CPU-hour2,190 RWF
Queue worker, 256 MiB182.5 GiB-hoursat 20 RWF per GiB-hour20 RWF per GiB-hour3,650 RWF
Queue worker CPU, 3% on average21.9 CPU-hoursat 30 RWF per CPU-hour30 RWF per CPU-hour657 RWF
Postgres backend, 1 GiB730 GiB-hoursat 20 RWF per GiB-hour20 RWF per GiB-hour14,600 RWF
Postgres backend CPU, 10% on average73 CPU-hoursat 30 RWF per CPU-hour30 RWF per CPU-hour2,190 RWF
Postgres data and storage, 10 GiB10 GiB-monthsat 150 RWF per GiB-month150 RWF per GiB-month1,500 RWF
Sign-in codes, 2,000 one-segment SMS2,000 segmentsat 15 RWF per segment15 RWF per segment30,000 RWF
Before the free allowance70,482 RWF
Free allowance: 50 GiB-hours of app memory-1,000 RWF
Free allowance: 5 CPU-hours of app CPU-150 RWF
The month69,332 RWF

Computed from BWEZE's published price list when this page was built. Memory is billed only while running; CPU only as used.

Two things stand out. Memory is most of the hosting bill, because it is billed for every hour a service is up whether or not it is busy. And once an app sends SMS, the messages can cost as much as the hosting: each segment is 15 RWF per segment, and a code that slips into two segments costs twice as much. The SMS cost breakdown shows how to keep codes to one.

Three changes that cut a bill most

Run jobs on a schedule instead of keeping a worker up. A worker that wakes once a night to send reports does not need to hold memory for the other 23 hours. As a cron job, it runs, is billed while it runs, and stops:

Cost exampleA nightly job instead of an always-on worker
WhatAmountRateCost
Job memory, 512 MiB for 10 minutes a night, 30 nights2.5 GiB-hoursat 20 RWF per GiB-hour20 RWF per GiB-hour50 RWF
Job CPU, half a CPU while it runs2.5 CPU-hoursat 30 RWF per CPU-hour30 RWF per CPU-hour75 RWF
Before the free allowance125 RWF
Free allowance: 2.5 GiB-hours of app memory-50 RWF
Free allowance: 2.5 CPU-hours of app CPU-75 RWF
The month0 RWF

Computed from BWEZE's published price list when this page was built. Memory is billed only while running; CPU only as used.

A run never overlaps the one before it, and it is stopped at its time limit (one hour unless you set another), so a stuck job cannot bill all month. See cron jobs in the docs.

Size memory to what the app uses. A Node or Python service that peaks at 300 MiB does not need 1 GiB. Halving a service’s memory halves that line.

Stop what you are not using. A staging app that only matters during the week can be stopped on Friday. Previews are billed only while they are open:

Cost examplePreviews for a busy week of pull requests
WhatAmountRateCost
10 previews, 256 MiB, open 8 hours each20 GiB-hoursat 20 RWF per GiB-hour20 RWF per GiB-hour400 RWF
Their CPU, 1% on average0.8 CPU-hoursat 30 RWF per CPU-hour30 RWF per CPU-hour24 RWF
Before the free allowance424 RWF
Free allowance: 20 GiB-hours of app memory-400 RWF
Free allowance: 0.8 CPU-hours of app CPU-24 RWF
The month0 RWF

Computed from BWEZE's published price list when this page was built. Memory is billed only while running; CPU only as used.

What is not on the bill

There is no monthly plan and no fee per seat. Domains are paid per year when you buy them. The wallet is prepaid, so the bill cannot run past what you put in: when the balance reaches zero, BWEZE emails the workspace’s owners and gives hosting 24 hours to top up before apps stop, with their configuration and data kept.

To work out your own month, start from the pricing page, which has every rate, or read the price list itself at api.bweze.com/v1/pricing.

Sources

Keep reading

All posts

Company · 4 min read

Introducing BWEZE: hosting, Postgres, SMS and DNS on one bill in RWF

One account for the stack a company in Rwanda runs, billed in francs from a wallet you top up with mobile money. What is in the beta, and what is not yet.

Engineering · 4 min read

Why BWEZE's ledger enforces its own rules in Postgres

Append-only entries, debits that must equal credits per currency, idempotency keys and holds on SMS sends, all checked by the database at commit time.

Company · 3 min read

Keeping personal data in Rwanda: what Law 058/2021 asks of your hosting

Rwanda's data protection law says personal data is stored in Rwanda unless the regulator certifies otherwise. What that means when you choose where an app runs.

Build the next thing, from Rwanda.

Get started