Self-host GlitchTip with Levelrail

A lightweight, self-hosted error tracking service compatible with the Sentry SDK.

How to self-host GlitchTip

  1. Pull the images

    3 images are pulled on your server.

    Show images
    • postgres:16-alpine
    • glitchtip/glitchtip:6.0
    • redis:7-alpine
  2. Create the app

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

  3. Fill in the secrets

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

GlitchTip requirements

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

Deploy GlitchTip your way

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

Deploy GlitchTip from the CLI

levelrail-cli templates deploy glitchtip --name my-glitchtip

Deploy GlitchTip 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/glitchtip/deploy

GlitchTip configuration

GlitchTip services

ServiceImagePortsVolumes
db postgres:16-alpine none glitchtip_db_data -> /var/lib/postgresql/data
glitchtip glitchtip/glitchtip:6.0 8080 none
redis redis:7-alpine none glitchtip_redis_data -> /data

GlitchTip environment variables

VariableServiceValue
POSTGRES_DB db Preset by the template
POSTGRES_PASSWORD db Generated at deploy
POSTGRES_USER db Preset by the template
DATABASE_URL glitchtip Generated at deploy
DEFAULT_FROM_EMAIL glitchtip Preset by the template
GLITCHTIP_DOMAIN glitchtip Preset by the template
REDIS_URL glitchtip Preset by the template
SECRET_KEY glitchtip Generated at deploy

Ports and volumes

Ports
8080
Volumes
2 named mounts: glitchtip_db_data -> /var/lib/postgresql/data, glitchtip_redis_data -> /data

GlitchTip FAQ

How much memory does GlitchTip need?

The catalog lists about 512 MiB of memory for GlitchTip across its 3 services.

Does GlitchTip run on arm64?

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

What licence is GlitchTip under?

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

Does GlitchTip need configuration before it starts?

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

Which database does GlitchTip bundle?

The template includes Postgres and Redis, running as its own service.

Which ports does GlitchTip use?

GlitchTip listens on port 8080 inside the stack.

Where does GlitchTip keep its data?

In named volumes: glitchtip_db_data mounted at /var/lib/postgresql/data and glitchtip_redis_data mounted at /data.

Can I deploy GlitchTip 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 glitchtip for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, glitchtip/glitchtip:6.0, redis:7-alpine is what you deploy there.

levelrail-cli templates deploy glitchtip --name my-glitchtip