FeaturesDocs Pricing
Contact us →
Feature • Security

Secure by default. From the first connect.

Every app runs in its own rootless Podman container, behind a firewall that allows only SSH, HTTP and HTTPS. Team roles, two-factor auth and passkeys control who gets in.

Rootless Podman containers Firewall: SSH, HTTP, HTTPS only Team roles, 2FA & passkeys Automatic Let's Encrypt SSL
security // srv-fra1.rubuz.host • Debian 13
Open ports: 22, 80, 443
Layer 01 // Perimeter 🛡️
Firewall

Only ports 22, 80 and 443 are reachable. Databases stay off the public internet.

✓ 3 ports open
Layer 02 // Transport 🔒
Let's Encrypt SSL

Every app domain gets a certificate that renews on its own. No certbot jobs to maintain.

✓ Auto-renewing
Layer 03 // Isolation 📦
Rootless Podman

Root inside the container maps to an unprivileged user outside. An escape does not get root on the host.

✓ Unprivileged UID map
Layer 04 // Access 🔑
Team Access

Roles decide who can deploy, back up and update. Sign in with two-factor auth or a passkey.

✓ 2FA + passkeys
Security checks
All checks passed
14:02:18 ✓
Firewall: Verified default policy DROP. Public exposure checked: Ports 22, 80, 443 only. All other incoming packets silently rejected.
14:02:19 ✓
Rootless Check: Verified subuid allocation (100000:65536). Container processes running with unprivileged capabilities only (CAP_NET_BIND_SERVICE dropped).
14:02:20 ✓
SSL: Let's Encrypt certificate for api.rubuz.cloud valid. Expiry in 89 days. Renewal scheduled.
14:02:21 ✓
Agentless: Scanned process table. Nothing from Rubuz left running. Session opened over SSH and closed after the task.
01 // Before and after

One hacked app should not mean a hacked server. With rootless containers, it does not.

Many setups run the Docker daemon as root. A bug in one app can then turn into root access on the whole server.

✕ Root Docker daemon

The usual setup

  • ✕
    Root daemon: Containers run under a daemon that runs as root. Escape one container and you may have the host.
  • ✕
    Firewall surprises: Docker writes its own iptables rules, which can expose a database port your firewall was meant to block.
  • ✕
    Apps can reach each other: On a shared network, one compromised container can probe the apps next to it.
  • ✕
    Shared logins: The whole team uses one account, so anyone can deploy, delete or reboot.
With Rubuz
✓ Rootless Podman

The Rubuz setup

  • ✓
    Rootless containers: Root inside a container is an unprivileged user on the host. Breaking out does not get an attacker root.
  • ✓
    Firewall stays in charge: Only SSH, HTTP and HTTPS are open. Databases run beside your apps without a public port.
  • ✓
    Apps kept apart: Each app has its own rootless container, so one compromised app cannot reach the others.
  • ✓
    Roles and 2FA: Decide who can deploy, back up and update. Add two-factor auth or a passkey to your sign-in.
02 // What you get

Security that is on from day one.

Nothing to switch on later. Every server you connect starts with the same setup.

Pillar 01

Rootless Podman containers

If an app has a vulnerability, the damage stays in its container. Rubuz maps root inside the container to an unprivileged user on the host.

What that means:
• No root Docker daemon on the host
• Each app in its own container
• One compromised app cannot reach the others
Pillar 02

A firewall with three open ports

When you connect a server, Rubuz sets up the firewall. Only ports 22 (SSH), 80 (HTTP) and 443 (HTTPS) are allowed in.

Firewall rules:
• Other incoming traffic is dropped
• Postgres, MySQL, Mongo and Valkey stay private
• No root daemon rewriting your rules
Pillar 03

Automatic Let's Encrypt SSL

Every app gets its own domain and a Let's Encrypt certificate. Renewals happen automatically, so certificates do not quietly expire.

Included:
• A certificate for every app domain
• Automatic renewal
• No certbot or Nginx config to maintain
Pillar 04

Team roles, 2FA and passkeys

Give each teammate only the access they need. Roles control who can deploy, run backups and apply updates.

Account protection:
• Roles for deploy, backup and update
• Two-factor authentication
• Passkeys for sign-in
Need more than one server?

Rubuz also runs managed Kubernetes on EKS, GKE, AKS, DOKS, VKE or LKE, in your own cloud account, with high availability, autoscaling and rolling deploys, from the same console as your servers.

Learn more
03 // Questions

Questions about security on Rubuz.

What is rootless Podman, and why is it safer than Docker? ↓

A standard Docker setup runs its daemon as root, so escaping one container can mean root on the host. Podman runs containers without a root daemon, and root inside a container maps to an unprivileged user on the host. An attacker who escapes does not land as root.

Can one compromised app read another app's database? ↓

No. Every app runs in its own rootless container, so a compromised app cannot reach the others. Databases run in their own containers beside the app, and the firewall keeps them off the public internet.

Does Rubuz leave open ports or background daemons running on my server? ↓

No. Rubuz connects over SSH, does the work and disconnects. Nothing is installed or left running, no extra ports are opened, and your apps keep running if you leave Rubuz.

How are SSL certificates handled? ↓

Rubuz issues a Let's Encrypt certificate for each app's domain and renews it automatically, so you do not have to track expiry dates.

Can I control who on my team can deploy? ↓

Yes. Team roles decide who can deploy, back up and update. Each person can protect their account with two-factor auth or a passkey.

From the blog: Why Rootless Containers Matter for VPS Security

Secure by default

Lock down every server. Without writing the rules yourself.

Connect a Debian 13 or Ubuntu 26.04 LTS server and it starts with rootless containers and a firewall.

✓ No card needed • 14-day free trial