Server security

Every server hardened from the start.

Beep sets up every server the same way: inbound traffic denied, app ports reachable only from its edge, security updates applied automatically, and containers restarted if they crash.

Get early access →Talk to us

Server security

Inbound: Denied by default
App traffic: From Beep’s edge only, encrypted
Updates: Unattended security updates, fail2ban
Recovery: Container restarts and drift repair

How it works.

Firewall on

Inbound traffic is denied by default. App ports are reachable only from Beep’s edge, over an encrypted private network.

Patched automatically

Unattended security updates and fail2ban are configured on every server.

Managed end to end

Beep owns the host setup, so nothing drifts and Beep stays responsible for its security.

Self-healing

Crashed containers restart. If a server drifts from what you deployed, Beep releases it back into shape.

See it run

The same setup on every server

Use Beep Cloud, your own cloud account, or any Ubuntu or Debian VPS. Beep installs its runtime and agent, locks the server down, and it is ready in minutes.

server setup · 203.0.113.12

→ ubuntu 24.04 · hetzner cx23 · fsn1

✓ firewall inbound denied by default

✓ hardened fail2ban · unattended upgrades

✓ runtime beep agent installed

✓ private network app ports reachable from beep’s edge only

server ready → edge.usebeep.sh

Server security, answered.

Straight answers. Anything missing, ask us directly.

Why can’t I SSH into the server?

So manual changes can’t conflict with Beep’s setup and Beep can stay responsible for security. Debug from a container shell in the dashboard instead.

Which servers get this setup?

Every server Beep manages: Beep Cloud, servers in your own cloud account, and any Ubuntu or Debian VPS you connect.

Guides that use it.

Deploy DockerBring your Dockerfile or a prebuilt image and run it on your own server, with zero-downtime releases, previews and automatic HTTPS.→Deploy DjangoDeploy Django with Gunicorn on your own server: migrations before every release, Postgres next to the app, and HTTPS on your domain.→

More features.

Preview environmentsEvery GitHub pull request gets its own environment and URL, running on your own servers and removed when the pull request closes. Developer and above include active previews.→Zero-downtime releasesBeep starts the new version first and moves traffic only once it passes its health checks. If something is wrong, roll back to an earlier image in one click, with no rebuild.→Managed databasesRun Postgres 16 to 18 with pgvector and PostGIS, plus Redis and Valkey, on the servers your apps already use. Back up to Beep’s storage or your own S3-compatible bucket.→Custom domains and HTTPSEvery service starts with a URL on edge.usebeep.sh. Point a CNAME at Beep and certificates are issued and renewed for you; you never touch a certificate file.→Logs and metricsLive-tail build and runtime logs. Track CPU, memory, requests, error rate and p95 latency for every service, and get an alert when errors or latency climb.→Static sitesHost static sites on Beep’s edge at no extra cost within your plan’s storage, with skew protection so visitors never mix old and new assets during a deploy.→

Own your infrastructure again.

Plans from $1 a month, billed per server, never per service.

Early access · We’ll set up your workspace

Or talk to us →