Cloud, simplified.
Rubuz runs your apps on any VPS, or on managed Kubernetes in your own cloud account. Push to deploy, install open-source apps in one click, and let Rubuz handle databases, SSL and backups, with nothing installed on your servers.
A PaaS bill, or a pile of scripts.
Every developer knows the trade-off. A managed PaaS is easy until the bill grows with every app, database and preview, and your code lives on someone else's platform. A plain VPS is cheap, but then you are the one writing deploy scripts, renewing certificates, patching packages and hoping the backup cron still runs.
Rubuz sits in between. Connect a server over SSH and point it at a GitHub repository. Every push builds on your own server and goes live only after the new container passes its health check. Each app runs in its own rootless Podman container, with Postgres, MySQL, MongoDB or Valkey beside it, Let's Encrypt certificates, and encrypted backups to your own S3 bucket.
Need n8n, Ghost, Metabase, Umami, Chatwoot, Vaultwarden or Open WebUI? Install them from the open-source app catalog in one click. Each gets its own container, domain, SSL and backups, on the same server as your code.
When one server is not enough, Rubuz runs managed Kubernetes clusters in your own DigitalOcean, Vultr or Linode account: high availability, autoscaling and rolling deploys, without the cost and complexity of EKS or GKE. Your provider bills you for the nodes directly, from the same console you already use.
Nothing is installed on the server. If you stop using Rubuz, your containers, databases and scheduled jobs keep running, because they are plain Podman containers and system services.
The people behind the code.
Systems, infrastructure, backend and frontend engineers, with design, QA and customer success alongside. Together we build and support Rubuz.
What we hold to.
Three rules every feature has to pass before it ships.
Your servers, your account
Your apps run on servers and cloud accounts you own, and you pay your provider directly. Rubuz holds an SSH key, not your workloads. Remove the key and everything keeps running.
Nothing proprietary
Podman containers, system services, Let's Encrypt and S3-compatible storage. Everything Rubuz sets up is something you can inspect over SSH and run yourself, so there is nothing to migrate off.
Secure by default
Rubuz connects over SSH only when it needs to and leaves nothing running. Every app gets a rootless container, the firewall leaves only SSH, HTTP and HTTPS open, and backups are encrypted before they leave the server.