How Rimbra works
One workspace for hosting, databases, domains, email and WhatsApp, and how the pieces fit together.
Your workspace
Everything you create lives in your workspace: projects, databases, domains, email senders, WhatsApp numbers and API keys. Nothing is shared with other accounts, and each product can use the others without extra setup. A project can read a database through an environment variable, serve a domain you bought here, and send email from that same domain.
The products
| Product | What it does | Where |
|---|---|---|
| Hosting | Builds and runs your apps from GitHub or uploaded files | Hosting → Projects |
| Databases | Managed PostgreSQL, MySQL and Redis | Hosting → Database |
| Domains | Buy domains or connect your own, with automatic HTTPS | Hosting → Domains |
| Emails | Transactional email and broadcasts from your own domain | Emails |
| Send and receive WhatsApp messages from your numbers | Social notifications → WhatsApp |
From code to a live app
- 1Source: Rimbra pulls your repository from GitHub or unpacks your upload.
- 2Detect: it reads your files to work out the framework and how to run it.
- 3Build: it installs dependencies and runs the build, logging every line.
- 4Run: static sites are served as files; servers start on their own port with your variables.
- 5Switch: once the new version answers, traffic moves to it. If anything fails, the previous version keeps serving.
APIs and keys
Email and WhatsApp each have their own API with their own keys, created in the dashboard. Keys belong to your workspace and can be revoked at any time. Call these APIs from your server, never from browser or mobile code.
| API | Base URL | Key from |
|---|---|---|
| Emails | https://api.rimbra.app/api/marketing/emails | Emails → API Keys |
| https://api.rimbra.app/ntf/v1 | WhatsApp → API |
Coming soon
Sandboxes, Buckets, Agents, MCP servers, email automations and brands are on the way. Their pages in the dashboard are marked Coming soon until they are ready.