Self-host Budibase with Levelrail

An open-source low-code platform for building internal tools, forms, and admin panels.

  • AuthorBudibase
  • LicenceGPL-3.0
  • Memory2 GiB
  • Archarm64
  • Services6

How to self-host Budibase

  1. Pull the images

    6 images are pulled on your server.

    Show images
    • budibase.docker.scarf.sh/budibase/apps:latest
    • budibase/couchdb:latest
    • ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Z
    • budibase/proxy:latest
    • redis:7-alpine
    • budibase.docker.scarf.sh/budibase/worker:latest
  2. Create the app

    6 services start in a single Compose app, with 3 named volume mounts for your data, on port 10000.

  3. Fill in the secrets

    19 secrets are generated and stored encrypted, 20 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Budibase requirements

Memory
About 2 GiB
Architectures
amd64 not available, arm64 image published
Ports
10000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
GPL-3.0, copyleft license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 10000 on the host, so open them in the VPS firewall only if you want that.
  • Review. Image is not pinned to a version tag, so a redeploy can pull different code (budibase.docker.scarf.sh/budibase/apps:latest, budibase.docker.scarf.sh/budibase/worker:latest, budibase/couchdb:latest, budibase/proxy:latest).

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Budibase. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Budibase docs page.

Deploy Budibase your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Budibase from the CLI

levelrail-cli templates deploy budibase --name my-budibase

Deploy Budibase with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/budibase/deploy

Budibase configuration

Budibase services

ServiceImagePortsVolumes
app-service budibase.docker.scarf.sh/budibase/apps:latest none none
couchdb-service budibase/couchdb:latest none budibase_couchdb_data -> /opt/couchdb/data
minio-service ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Z none budibase_minio_data -> /data
proxy-service budibase/proxy:latest 10000 none
redis-service redis:7-alpine none budibase_redis_data -> /data
worker-service budibase.docker.scarf.sh/budibase/worker:latest none none

Budibase environment variables

VariableServiceValue
API_ENCRYPTION_KEY app-service Generated at deploy
BUDIBASE_ENVIRONMENT app-service Preset by the template
COUCH_DB_URL app-service Generated at deploy
ENCRYPTION_KEY app-service Generated at deploy
INTERNAL_API_KEY app-service Generated at deploy
JWT_SECRET app-service Generated at deploy
LOG_LEVEL app-service Preset by the template
MINIO_ACCESS_KEY app-service Generated at deploy
Show all 39 variables
  • MINIO_SECRET_KEYapp-serviceGenerated at deploy
  • MINIO_URLapp-servicePreset by the template
  • PORTapp-servicePreset by the template
  • REDIS_URLapp-servicePreset by the template
  • SELF_HOSTEDapp-servicePreset by the template
  • WORKER_URLapp-servicePreset by the template
  • COUCHDB_PASSWORDcouchdb-serviceGenerated at deploy
  • COUCHDB_USERcouchdb-serviceGenerated at deploy
  • TARGETBUILDcouchdb-servicePreset by the template
  • MINIO_BROWSERminio-servicePreset by the template
  • MINIO_ROOT_PASSWORDminio-serviceGenerated at deploy
  • MINIO_ROOT_USERminio-serviceGenerated at deploy
  • APPS_UPSTREAM_URLproxy-servicePreset by the template
  • COUCHDB_UPSTREAM_URLproxy-servicePreset by the template
  • MINIO_UPSTREAM_URLproxy-servicePreset by the template
  • RESOLVERproxy-servicePreset by the template
  • WORKER_UPSTREAM_URLproxy-servicePreset by the template
  • API_ENCRYPTION_KEYworker-serviceGenerated at deploy
  • APPS_URLworker-servicePreset by the template
  • CLUSTER_PORTworker-servicePreset by the template
  • COUCH_DB_PASSWORDworker-serviceGenerated at deploy
  • COUCH_DB_URLworker-serviceGenerated at deploy
  • COUCH_DB_USERNAMEworker-serviceGenerated at deploy
  • INTERNAL_API_KEYworker-serviceGenerated at deploy
  • JWT_SECRETworker-serviceGenerated at deploy
  • MINIO_ACCESS_KEYworker-serviceGenerated at deploy
  • MINIO_SECRET_KEYworker-serviceGenerated at deploy
  • MINIO_URLworker-servicePreset by the template
  • PORTworker-servicePreset by the template
  • REDIS_URLworker-servicePreset by the template
  • SELF_HOSTEDworker-servicePreset by the template

Ports and volumes

Ports
10000
Volumes
3 named mounts: budibase_couchdb_data -> /opt/couchdb/data, budibase_minio_data -> /data, budibase_redis_data -> /data

Budibase FAQ

How much memory does Budibase need?

The catalog lists about 2 GiB of memory for Budibase across its 6 services.

Does Budibase run on arm64?

For Budibase, an arm64 image is published; amd64 is not available.

What licence is Budibase under?

Budibase is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.

Does Budibase need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does Budibase bundle?

The template includes Redis, running as its own service.

Which ports does Budibase use?

Budibase listens on port 10000 inside the stack.

Where does Budibase keep its data?

In named volumes: budibase_couchdb_data mounted at /opt/couchdb/data, budibase_minio_data mounted at /data and budibase_redis_data mounted at /data.

Can I deploy Budibase on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id budibase for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image budibase.docker.scarf.sh/budibase/apps:latest, budibase/couchdb:latest, ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Z, budibase/proxy:latest, redis:7-alpine, budibase.docker.scarf.sh/budibase/worker:latest is what you deploy there.

levelrail-cli templates deploy budibase --name my-budibase