Self-host Umami with Levelrail

Verified

Simple, privacy-focused website analytics without tracking cookies or ad-tech.

  • Authorumami-softwareVerified by Levelrail
  • LicenceMIT
  • Memory512 MiB
  • Archarm64
  • Services2

How to self-host Umami

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • postgres:16-alpine
    • ghcr.io/umami-software/umami:postgresql-v2.19.0
  2. Create the app

    2 services start in a single Compose app, with 1 named volume mount for your data, on port 3000.

  3. Fill in the secrets

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

Umami requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 tested
Ports
3000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Verified. Verified on arm64 with image tag postgresql-v2.19.0. Our CI ran this exact image version and it answered on its health path. Evidence
  • Host ports. It publishes port 3000 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 Umami. 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 Umami docs page.

Deploy Umami your way

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

Deploy Umami from the CLI

levelrail-cli templates deploy umami --name my-umami

Deploy Umami 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/umami/deploy

Umami configuration

Umami services

ServiceImagePortsVolumes
db postgres:16-alpine none umami_db_data -> /var/lib/postgresql/data
umami ghcr.io/umami-software/umami:postgresql-v2.19.0 3000 none

Umami environment variables

VariableServiceValue
POSTGRES_DB db Preset by the template
POSTGRES_PASSWORD db Generated at deploy
POSTGRES_USER db Preset by the template
APP_SECRET umami Generated at deploy
DATABASE_TYPE umami Preset by the template
DATABASE_URL umami Generated at deploy

Ports and volumes

Ports
3000
Volumes
1 named mount: umami_db_data -> /var/lib/postgresql/data

Umami FAQ

How much memory does Umami need?

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

Does Umami run on arm64?

For Umami, arm64 is tested; amd64 is image published.

What licence is Umami under?

Umami is licensed under MIT, which is permissive, with few conditions on reuse.

Does Umami need configuration before it starts?

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

Which database does Umami bundle?

The template includes Postgres, running as its own service.

Which ports does Umami use?

Umami listens on port 3000 inside the stack.

Where does Umami keep its data?

In a named volume: umami_db_data mounted at /var/lib/postgresql/data.

Can I deploy Umami 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 umami for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, ghcr.io/umami-software/umami:postgresql-v2.19.0 is what you deploy there.

levelrail-cli templates deploy umami --name my-umami