Pricing
The plans (Free, Hobby, Pro, Enterprise), what each meter costs in RWF, the free monthly allowance, and how usage is measured and charged.
BWEZE charges for what runs, at one public price list, from your workspace's prepaid wallet. Free has no minimum; Hobby and Pro take a monthly minimum and give all of it back as usage credit.
Plans
| Plan | Monthly minimum | Projects | Backends | Custom domains | Members | Live previews |
|---|---|---|---|---|---|---|
| Free | none | 1 | 1 | 1 | 1 | 0 |
| Hobby | 10,000 RWF | 5 | 2 | 5 | 3 | 3 |
| Pro | 30,000 RWF | 25 | 10 | 50 | 25 | 10 |
| Enterprise | by contract | by contract | by contract | by contract | by contract | by contract |
On Free, a web service sleeps after 15 minutes without a request and wakes on the next one; on a paid plan services stay always on unless you choose otherwise (Sleep when idle).
The minimum is paid on the 1st and comes back as usage credit for hosting
and SMS that month; usage beyond it is paid from the wallet at the prices
below. Limits count what a workspace has at once (*.bweze.app names are not
custom domains). Plans are in the published list too (plans), with the same
30 days' notice for a higher minimum or a lower limit. How credit, plan
changes and renewals work: Billing.
Prices
| Meter | Price (RWF) |
|---|---|
| App memory | 20 per GiB-hour |
| App CPU | 30 per CPU-hour |
| Backend memory | 20 per GiB-hour |
| Backend CPU | 30 per CPU-hour |
| Backend storage | 150 per GiB-month |
| SMS | 15 per segment (how segments count) |
| Domains | per year, by suffix (price list) |
The published list is the authority, readable without a token:
curl https://api.bweze.com/v1/pricingIt returns the list in force (current) and any list already announced
(scheduled). A price only goes up with 30 days' notice, and a new list never
applies to usage before it.
Free allowance
Each workspace gets 50 GiB-hours of app memory and 5 CPU-hours of app CPU free every UTC month, once it is unlocked:
- A workspace owner verifies a Rwandan mobile number (
+250 72,73,78or79). - On Billing, they click Unlock for this workspace.
A number unlocks the allowance for one workspace, for good; deleting the workspace or changing the number does not free it for another. Without the allowance, a workspace can still top up and pay as it goes. The allowance covers app usage only, not backends, SMS or domains.
How usage is measured
- Memory is charged as configured, and only while the service is running: a 512 MiB service costs the same busy or idle, and nothing while it is stopped or asleep.
- A sleeping service has nothing running, so it costs nothing until a request wakes it. Its idle window before it sleeps (15 minutes on Free) is charged like any running time (Sleep when idle).
- CPU is charged for the CPU time actually used.
- Storage is charged as provisioned, whether the backend is busy, idle or stopped.
- Jobs, cron runs and pre-deploy commands are charged like their service while they run.
Usage is sampled every hour and charged to the wallet once each UTC day has ended. Until then it shows as unsettled usage and already counts against your available balance.
An example
One web service at the default size (0.5 CPU, 512 MiB) running all month (about 730 hours) uses 365 GiB-hours of memory:
| Memory: 365 GiB-hours - 50 free = 315 × 20 RWF | 6,300 RWF |
| CPU: 20 CPU-hours used - 5 free = 15 × 30 RWF | 450 RWF |
| Month | 6,750 RWF |
The CPU line depends on your traffic; a mostly idle service uses far less than its 0.5 CPU.
On Free the same service sleeps when it has no visitors. If it gets visitors for about two hours a day, it runs about 2¼ hours a day with its 15-minute wind-down: about 34 GiB-hours of memory a month, inside the 50 free.