Self-host NocoBase with Levelrail

An extensible no-code/low-code platform for building internal tools and databases.

  • Authornocobase
  • LicenceLicenseRef-NocoBase
  • Memory1 GiB
  • Archarm64
  • Services2

How to self-host NocoBase

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • nocobase/nocobase:1.9.33
    • postgres:17-alpine
  2. Create the app

    2 services start in a single Compose app, with 2 named volume mounts for your data, on port 13000.

  3. Fill in the secrets

    3 secrets are generated and stored encrypted, 7 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.

NocoBase requirements

Memory
About 1 GiB
Architectures
amd64 image published, arm64 image published
Ports
13000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
LicenseRef-NocoBase, source available
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 13000 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then NocoBase. 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 NocoBase docs page.

Deploy NocoBase your way

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

Deploy NocoBase from the CLI

levelrail-cli templates deploy nocobase --name my-nocobase

Deploy NocoBase 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/nocobase/deploy

NocoBase configuration

NocoBase services

ServiceImagePortsVolumes
nocobase nocobase/nocobase:1.9.33 13000 nocobase_storage -> /app/nocobase/storage
postgres postgres:17-alpine none nocobase_postgres_data -> /var/lib/postgresql/data

NocoBase environment variables

VariableServiceValue
APP_KEY nocobase Generated at deploy
DB_DATABASE nocobase Preset by the template
DB_DIALECT nocobase Preset by the template
DB_HOST nocobase Preset by the template
DB_PASSWORD nocobase Generated at deploy
DB_PORT nocobase Preset by the template
DB_USER nocobase Preset by the template
POSTGRES_DB postgres Preset by the template
Show all 10 variables
  • POSTGRES_PASSWORDpostgresGenerated at deploy
  • POSTGRES_USERpostgresPreset by the template

Ports and volumes

Ports
13000
Volumes
2 named mounts: nocobase_storage -> /app/nocobase/storage, nocobase_postgres_data -> /var/lib/postgresql/data

NocoBase FAQ

How much memory does NocoBase need?

The catalog lists about 1 GiB of memory for NocoBase across its 2 services.

Does NocoBase run on arm64?

For NocoBase, an arm64 image is published; amd64 is image published.

What licence is NocoBase under?

NocoBase is licensed under LicenseRef-NocoBase, which is source-available, so read the terms before commercial use.

Does NocoBase need configuration before it starts?

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

Which database does NocoBase bundle?

The template includes Postgres, running as its own service.

Which ports does NocoBase use?

NocoBase listens on port 13000 inside the stack.

Where does NocoBase keep its data?

In named volumes: nocobase_storage mounted at /app/nocobase/storage and nocobase_postgres_data mounted at /var/lib/postgresql/data.

Can I deploy NocoBase on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for NocoBase, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image nocobase/nocobase:1.9.33, postgres:17-alpine is what you deploy there.

levelrail-cli templates deploy nocobase --name my-nocobase