Start with the docs
docs.bweze.com covers deploys, Postgres backends, SMS, DNS and the API. Every error BWEZE returns carries a stable code and a link to the docs page that explains it, so the answer is often one click away.
Write to us
- [email protected] for anything about BWEZE: a question, the beta, your bill, Enterprise, or help moving in.
- [email protected] for vulnerabilities only. Read thesecurity page first.
What to send
One message with these usually gets an answer in one reply:
- Your workspace name.
- The project, deploy or message it is about, with its ID if you have it.
- The error, as BWEZE returned it: the
codeand thedocslink. - What you expected, and what happened instead.
- For a question about your bill: the date and the amount of the top-up or charge.
Every API error has the same shape, so the code is easy to find:
{ "error": { "code": "insufficient_balance", "message": "...", "docs": "https://docs.bweze.com/errors/insufficient_balance" } }Moving a team or an agency
Tell us what you run today: where your apps are hosted, which database, which SMS provider and where your domains live. We will tell you what moves as it is and what needs work before you switch. Apps deploy from a git repository or a Dockerfile, and a Postgres database moves with pg_dump and pg_restore.
When something looks down
BWEZE has no public status page yet; this page will link to it when there is one. Until then, if something looks down, write to [email protected] with the time it started and what you saw.