Deploy Docker on your own server.

Step by step.

1. 01

   Connect a server

   Use Beep Cloud, a server in your own cloud account, or any Ubuntu or Debian VPS. Beep installs its runtime and agent and locks the server down: inbound traffic is denied, and app ports are reachable only from Beep’s edge.

2. 02

   Create a service from your repository

   Pick the GitHub or GitLab repository and the branch to track. In a monorepo, set the root directory for this service; watch paths limit rebuilds to changes that touch it.

3. 03

   Let Beep build it

   Set the build to Dockerfile and point Beep at its path, or deploy a prebuilt image by tag. You can override the install, build or start command on the service.

   Your image’s CMD, or a start command that overrides it

4. 04

   Listen on $PORT

   Beep sets PORT for every service unless you set it yourself, and routes traffic from its edge to that port. Bind to 0.0.0.0 so the edge can reach the container.

   # listen on 0.0.0.0:$PORT inside the container
   ENV PORT=8080
   CMD ["./server"]

5. 05

   Add a database

   Add managed Postgres (16 to 18, with pgvector and PostGIS), Redis or Valkey to the project, then reference its connection string from your service. References resolve at deploy time.

   DATABASE_URL=${{ postgres.DATABASE_URL }}
   REDIS_URL=${{ redis.REDIS_URL }}

6. 06

   Set a health check and deploy

   Set the health check path to /health. Every push to the tracked branch builds and releases; traffic moves to the new version only once it passes, and rolling back re-releases an earlier image without a rebuild.

7. 07

   Add your domain

   Every service starts with a URL on edge.usebeep.sh. When it works, point a CNAME for your domain at Beep; the certificate is issued and renewed for you. Each GitHub pull request also gets its own preview environment, removed when it closes.