Private mesh networking
Servers talk to each other over an encrypted private network. Only the load balancer faces the internet.
Where it runs
Four regions, two providers
Choose the region closest to your users when you create a Project. Your data stays there — RustaBase does not move it somewhere else to balance a queue.
AWSHetzner
Deployed on trusted infrastructure- United States
- Germany
- Finland
- Singapore
Isolation
What your Project keeps to itself
Isolation is not a setting you turn on. It is how a Project is created — the parts that hold your data and run your code belong to that Project alone.
| Your Project has its own | What that means |
|---|---|
| PostgreSQL database | Data, users, files, and settings live in a database that belongs to your Project alone. |
| Isolated compute environment | Your backend runs in its own space on Kubernetes, apart from every other Project. |
| Secrets and API keys | Server-side keys stay inside your Project and are never sent to browsers or end users. |
| Domains and certificates | Each custom domain gets its own HTTPS certificate, issued and renewed automatically. |
| Firewall rules | IP rules, country blocks, rate limits, and bot protection apply to your app only. |
| Logs and metrics | Activity, health, and usage charts show only your Project's own traffic. |
What is shared: the machines themselves, at AWS and Hetzner, and the console you sign in to. Nothing that stores your data or runs your code is shared with another Project.
Security by default
Three things you do not have to configure
Every Project gets these from the first deployment, on every plan.
Isolated project backends
Every project runs in its own isolated space on Kubernetes, with its own PostgreSQL database.
HTTPS everywhere
Automatic certificates and encrypted traffic for every app, domain and API — secure by default.
One request, start to finish
How a visitor reaches your data
Follow a single request from a browser to the database behind your app.
- 01
A visitor opens your app
Their browser connects over HTTPS. Certificates are managed for you, so there is nothing to install or renew.
- 02
Traffic reaches the load balancer
The load balancer is the only RustaBase machine that faces the public internet. Everything else sits behind it.
- 03
Requests cross a private network
Our servers talk to each other over an encrypted private mesh, not over the open internet.
- 04
Your application answers
The request arrives in the isolated environment that runs your Project — and only your Project.
- 05
Data comes from your database
Your app reads and writes its own PostgreSQL database, in the region you chose.
Availability and your data
What we commit to in writing
The promises below live in our legal pages and docs, not only on this page.
Availability
Paid plans target at least 99.9% monthly availability of Project APIs and databases. The Free plan carries no uptime commitment.
Read the SLAData location
Your Project's data stays in the region you select. Where a transfer outside the EEA, UK, or Switzerland is needed, the EU Standard Contractual Clauses apply.
Read the DPABackups and recovery
Plans that include backups take them on a schedule. You can download a backup and restore it from the same console.
See backupsBuilt with open source
Built with open source
RustaBase is built primarily with Rust, Go, and PostgreSQL. Thank you to these projects.
Run on it today
Your own backend, on infrastructure you can describe.
Create a Project, pick a region, and ship with HTTPS, isolation, and backups already in place.