Self-host Planka with Levelrail

A Trello-style kanban board for visualizing and tracking work across a team.

  • Authorplankanban
  • LicenceLicenseRef-PLANKA-Community
  • Memory512 MiB
  • Archarm64
  • Services2

How to self-host Planka

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • postgres:16-alpine
    • ghcr.io/plankanban/planka:2.2.1
  2. Create the app

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

  3. Fill in the secrets

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

Planka requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 image published
Ports
1337
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
LicenseRef-PLANKA-Community, 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 1337 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 Planka. 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 Planka docs page.

Deploy Planka your way

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

Deploy Planka from the CLI

levelrail-cli templates deploy planka --name my-planka

Deploy Planka 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/planka/deploy

Planka configuration

Planka services

ServiceImagePortsVolumes
db postgres:16-alpine none planka_db_data -> /var/lib/postgresql/data
planka ghcr.io/plankanban/planka:2.2.1 1337 planka_data -> /app/data

Planka environment variables

VariableServiceValue
POSTGRES_DB db Preset by the template
POSTGRES_PASSWORD db Generated at deploy
BASE_URL planka Preset by the template
DATABASE_URL planka Generated at deploy
SECRET_KEY planka Generated at deploy

Ports and volumes

Ports
1337
Volumes
2 named mounts: planka_db_data -> /var/lib/postgresql/data, planka_data -> /app/data

Planka FAQ

How much memory does Planka need?

The catalog lists about 512 MiB of memory for Planka across its 2 services.

Does Planka run on arm64?

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

What licence is Planka under?

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

Does Planka need configuration before it starts?

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

Which database does Planka bundle?

The template includes Postgres, running as its own service.

Which ports does Planka use?

Planka listens on port 1337 inside the stack.

Where does Planka keep its data?

In named volumes: planka_db_data mounted at /var/lib/postgresql/data and planka_data mounted at /app/data.

Can I deploy Planka 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 Planka, 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 postgres:16-alpine, ghcr.io/plankanban/planka:2.2.1 is what you deploy there.

levelrail-cli templates deploy planka --name my-planka