Deploy Bun

Deploy Bun on your own server.

Deploy a Bun server on your own machine: installs with Bun, Postgres through Bun’s built-in SQL client, and health-checked releases with no downtime.

Bun on Beep
Build
Railpack (auto)
Start
bun run start
Port
$PORT, set by Beep
Pre-deploy
bun run db:migrate
Health check
/health

Step by step.

  1. 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. 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. Let Beep build it

    Beep detects Bun from bun.lock and installs your dependencies with Bun. You can override the install, build or start command on the service.

    Start command
    bun run start
  4. 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.

    server.ts
    Bun.serve({
      port: Number(process.env.PORT) || 3000,
      hostname: "0.0.0.0",
      fetch: (req) => new Response("ok"),
    })
  5. 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.

    db.ts
    import { SQL } from "bun"
    
    export const db = new SQL(process.env.DATABASE_URL!)
    // DATABASE_URL=${{ postgres.DATABASE_URL }}
  6. Run migrations before each release

    Set a pre-deploy command. It runs before each release, so the schema is ready before the new version takes traffic.

    Pre-deploy command
    bun run db:migrate
  7. 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.

  8. 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.

Bun tips.

Point db:migrate at your migration tool (Drizzle, Prisma or your own script) and set it as the pre-deploy command.

Bun’s built-in SQL client talks to Postgres directly, with no extra driver.

Run queue consumers as a separate worker service with its own start command.

Bun on Beep, answered.

Straight answers. Anything missing, ask us directly.

Do I need a Dockerfile to deploy Bun?

No. Beep detects Bun from bun.lock and installs your dependencies with Bun. If your project already has a Dockerfile, you can build with that instead.

Where does the Bun app run?

On the server you connected: Beep Cloud, your own cloud account or any Ubuntu or Debian VPS. Beep bills per server, so databases, workers and previews on the same server add nothing to the plan.

Can I SSH into the server?

No, and that’s deliberate: Beep manages each host end to end so manual changes can’t drift from its setup. To debug, open a shell inside any container from the dashboard, next to its logs and metrics.

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 →