Apps & backends
Push code. It’s live. Every push builds a container and goes live on bweze.app, with preview URLs, one-click rollback and a Postgres backend beside it.
Read the docsPay in your currency.
Built in Africa.
Push code. It’s live. Every push builds a container and goes live on bweze.app, with preview URLs, one-click rollback and a Postgres backend beside it.
Read the docsReach every phone in Rwanda. Verification codes, alerts and notifications to MTN and Airtel, with a delivery receipt for each.
See SMSEvery record in one place. Authoritative DNS with an API and DNSSEC, run from Rwanda. .rw registration once we are accredited.
See domains20 RWF a GiB-hour of memory, only while your app runs. CPU for the time it uses, storage for what you provision. Stopped apps cost nothing.
A CLI, a plain REST API, llms.txt and a Markdown copy of every guide. Idempotency keys on anything that spends or sends.
Top up with mobile money or card, in your currency. Every price is public, with 30 days’ notice before an increase.
Standard Postgres, the S3 API and Dockerfiles. Your app and your data move when you do.
The tools teams usually glue together by hand come with every project, from the first push.
Every pull request gets its own live URL, so the change is reviewed before it merges.
Put any earlier deploy back live in one click when a release goes wrong.
Next, Node, Python and Go are detected and built for you. No build scripts to write.
Watch the build while it runs. A failed build tells you why.
Postgres with auth, storage, realtime and pgvector, next to your app.
Migrations run before a release goes live. If they fail, the last release stays up.
Commands on a schedule, workers that never sleep, and one-off jobs on the live release.
Environment variables for build and runtime, encrypted at rest.
Connect your own domain with two DNS records. Every app is served over HTTPS.
Internal APIs and caches that only your other services can reach.
Run a command inside the running container, from the dashboard or the API.
Do what the dashboard does from your terminal, or through one API with an OpenAPI spec.
$ npx @bweze/cli login
Infrastructure only matters when it runs where your customers are, and bills in the money they use.
The stack a production app runs on, placed and priced for builders across Africa.
Connect a repo and every push builds a container and goes live on bweze.app. Zero-config builds, preview URLs, one-click rollback to any earlier deploy.
Every project gets Postgres with auth, object storage, row-level security and pgvector. The beta will back up every database nightly and drill restores: up to a day of data at risk, and we say so.
One HTTP API for MTN and Airtel phones in Rwanda, with delivery receipts and opt-outs handled. Billed per segment, never sent on credit.
Authoritative DNS with a real API and one-click DNSSEC. .rw registration through BWEZE the moment we are accredited.
Startups, software teams and the agencies that ship for them, building web and mobile products across Africa. One account covers hosting, Postgres backends, SMS and DNS, on one bill.
Memory only while the app runs, CPU for the time it uses, and storage for what you provision. A stopped app costs nothing. Every rate is on one public, versioned price list, and an increase is published at least 30 days before it takes effect.
Hosting gets a 24-hour grace to top up, then stops without touching your data, and starts again when you top up. SMS refuses a send it cannot pay for. BWEZE never runs on credit, so there is never a debt.
Yes. Connect a git repository: Next, Node, Python and Go build with no config, and a Dockerfile works too. A Postgres database moves with pg_dump and pg_restore; auth users, storage objects and the code that calls them need their own check before you switch.
No. Your app is a container, your database is standard Postgres and your files sit behind the S3 API, so each of them leaves the way it came in.
Judge it by what it says plainly: the beta runs in one data center, there is no SLA until we can measure one, and the nightly backup job is not running yet, so keep your own pg_dump of anything you cannot lose.
Yes. Everything works through the CLI or a REST API with an OpenAPI spec, errors come back as JSON with a stable code and a docs link, calls that spend or send take an idempotency key, and the docs are published as llms.txt and Markdown.
Moving a team or an agency? Talk to us.