Skip to content

Deploy Bun

Deploy a Bun app on Ownkube in minutes. Push your repo and Ownkube builds it and ships it, and you get a live URL with automatic TLS. Managed Postgres, logs, metrics, and one-click rollbacks come built in. No cloud account to start.

  • A Bun app in a GitHub or GitLab repository
  • About five minutes
  1. Connect your repo

    Sign in at app.ownkube.io/login, open Settings, and connect the GitHub App (or GitLab) so Ownkube can reach your repository. Already have a prebuilt image in a registry? Point Ownkube at it instead. See Registries.

  2. Create a Web deployment

    From your dashboard, choose Create deployment, pick Web, and select your Bun repo. Ownkube builds it and pushes the image to a registry it manages for you.

  3. Set the port

    Pass hostname: "0.0.0.0" to Bun.serve, not localhost, so the app is reachable. 3000 is a common default; set that as the port so traffic routes to your app. You can change it later in Settings.

  4. Add environment variables

    Add any KEY=value pairs your app reads, and mark secrets with the Secret toggle. See Environment variables.

  5. Deploy

    Click Create deployment. The deployment page streams the build, then startup and health checks. When the status goes healthy, open the generated hostname on the Overview tab. Your Bun app is live, with TLS included.

Port 3000

Whatever port you pass to Bun.serve should match the port you set in Ownkube. 3000 is a common default.

Bun.serve host

Pass hostname: "0.0.0.0" to Bun.serve so the server accepts connections from outside the container.

Add a database

Bun ships a built-in Postgres client, or use your favorite driver. Attach a database in a click and read DATABASE_URL.

Bring your own Dockerfile

Want full control of the build? Add a Dockerfile to your repo and Ownkube uses it, reading the port from its EXPOSE line.

Need Postgres? Add a Database in one click and Ownkube injects the connection string as DATABASE_URL (plus PGHOST, PGUSER, and friends) into your app. See Databases.

Once you’re running, turn on autoscaling on CPU and memory, watch logs and metrics on every deployment, and roll back a bad deploy in one click.