1. BWEZE
  2. Blog
  3. Company

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.

A software company in Kigali usually rents its infrastructure from five vendors. Hosting comes from one, the database from a second, SMS from a local gateway, the domain from a registrar abroad, and DNS from whoever was cheapest the day it was set up. That makes five logins and five invoices, in four currencies, and most of them want a card.

BWEZE puts that stack in one account. You deploy from Git, give the app a Postgres backend, send SMS to MTN and Airtel phones and manage the domain, and it all comes out of one wallet in Rwandan francs that you top up with mobile money.

What is in it

Deploy. Push a repository and it is live on a bweze.app address with HTTPS. A service can be a public web service, a private service that only your other services reach, a background worker or a cron job. Web services get a preview for each pull request and take custom domains. A pre-deploy command (a migration, say) runs before each release goes live, and if it fails the release that was live stays live.

Postgres backends. A backend project is a data stack: Postgres with auth, storage, realtime and pgvector. It is standard Postgres, so your tools and your dumps work as they do anywhere else.

SMS. One call, POST /v1/messages, sends to a Rwandan number. Templates fill in codes, an idempotency key makes a retry return the first result instead of sending twice, and a preview call tells you how many segments a message is before you pay for it. Each message reports queued, sent, then delivered or failed as receipts come back. Recipients can opt out by texting STOP, or hangana or guhagarara in Kinyarwanda.

Domains. Search a name across .com, .app, .dev, .io, .co, .xyz and .rw, buy it from the wallet, and it is registered in your name, with its DNS on BWEZE’s nameservers and connected to your project. BWEZE is working toward accreditation with RICTA, the .rw registry, so that it can register .rw names directly. Until then, a .rw purchase is completed by hand.

How it is billed

There is no monthly plan. You pay for what runs, at the rates on the published price list:

  • memory at 20 RWF per GiB-hour, only while the app is running;
  • CPU at 30 RWF per CPU-hour, for the CPU time actually used;
  • backend storage at 150 RWF per GiB-month;
  • SMS at 15 RWF per segment.

A stopped app costs nothing. Each workspace also gets 50 GiB-hours of app memory and 5 CPU-hours of app CPU free each month, once its owner verifies a Rwandan mobile number.

The wallet is prepaid, so it stops at zero instead of running up a debt. Hosting gets 24 hours’ grace to top up before apps stop; their data is kept. A price can only go up after 30 days’ notice on the price list, which is public at api.bweze.com/v1/pricing.

Built for agents as well as people

Everything the dashboard does is a REST call with a bearer key, and the CLI (npx @bweze/cli login) drives the same API. Errors come back as JSON with a stable code and a link to the docs page that explains them. Anything that spends money or sends a message takes an idempotency key, so an agent that retries cannot pay twice. The docs publish llms.txt and a Markdown copy of every page, and so do these sites.

What is not done yet

We would rather say this here than have you find it later.

  • The beta will run in one data center in Kigali. One data center means one place that can fail, and we will say so on the status page when there is one. There is no status page yet.
  • Backups are not running yet. Until the nightly backup job runs, we do not describe backups as a feature.
  • There is no SLA. We will not offer one until we can measure it.
  • .rw registration through BWEZE depends on RICTA accreditation, which is not complete.

Joining the beta

The beta opens to companies on the waitlist first. Join it on bweze.com, read the pricing page for every rate, or read the docs to see the API before you sign up.

Sources

Keep reading

All posts

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.

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