AltFreeStack
Monitoring, Logs & Errorsdocker-readypermissive-license100% FOSSπŸ”΄ Full Β· ~2GB

GlitchTip: Open Source alternative to Sentry in 2026

GlitchTip is compatible with the Sentry SDK but with a much lighter backend β€” you just change the DSN URL, no app code changes needed.

License MIT2.5k stars(estimated)Website GitHub Repository

Audit Snapshot

  • License β€” Not verifiable on GitHub

  • GitHub β€” No live data

  • Latest release β€” Not available

  • Docker Compose β€” Not verified

  • Production β€” Not production-tested by AltFreeStack

GlitchTip vs. Sentry

Pros

  • The ideal balance between lightweight and Sentry-compatible

Things to consider

  • Fewer advanced features than Sentry (no full performance tracing)

Quick Docker installation guide

Copy this docker-compose.yml, adjust the example passwords and run docker compose up -d on your server. See the full step-by-step guide β†’

πŸ’‘ Official SaaS or self-hosted with AltFreeStack?

  • On the official cloud: a recurring monthly fee and usage limits on Sentry.
  • On your own VPS: 100% free software on your own server, with no artificial row, project or user limits.
docker-compose.yml
services:
  postgres:
    image: postgres:16-alpine
    environment:
      POSTGRES_PASSWORD: change-me
      POSTGRES_DB: glitchtip
  redis:
    image: redis:alpine
  web:
    image: glitchtip/glitchtip:6.2.6
    environment:
      DATABASE_URL: "postgres://postgres:change-me@postgres:5432/glitchtip"
      SECRET_KEY: "change-me-super-secret"
      REDIS_URL: "redis://redis:6379/0"
      EMAIL_URL: "consolemail://"
    ports:
      - "8000:8000"
  worker:
    image: glitchtip/glitchtip:6.2.6
    command: ./bin/run-celery-with-beat.sh
    environment:
      DATABASE_URL: "postgres://postgres:change-me@postgres:5432/glitchtip"
      SECRET_KEY: "change-me-super-secret"
      REDIS_URL: "redis://redis:6379/0"

πŸš€ Deploy in 1 command

Recommended for beginners

Copy this single command and paste it into your freshly created VPS's console (Vultr, DigitalOcean...). It downloads the script, prints it to your screen so you can see exactly what it's about to do (never a blind direct pipe), and only then installs Docker if needed, writes the files with secrets already generated, and starts everything β€” no nano, no pasting code blocks.

curl -sSL ".../api/deploy?stack=glitchtip" -o deploy.sh && cat deploy.sh && bash deploy.sh

We couldn't read the repository's recent activity from GitHub right now.

This docker-compose not working for you? Report it on GitHub β†’

Technical profile

License
MIT
Category
Monitoring, Logs & Errors
Replaces
Sentry
Tech stack
DjangoPostgreSQLCelery

Key features

  • Compatible with the Sentry SDK with no changes
  • Much lighter than Sentry self-hosted
  • Email/Slack notifications

Preview

GlitchTip interface preview

Public image provided by GlitchTip on its own website.

πŸ’Ύ Backups in 3 steps (Day 2)

As long as the ./data folder (the "volume" mapped into the container) exists on your server, your data survives any restart or container update β€” that's the only thing you need to back up.

1. Create a compressed backup on the server

tar -czvf backup-$(date +%F).tar.gz ./data

2. Download it to your computer

From your computer's terminal (not your server's):

scp root@YOUR_IP:~/app/backup-*.tar.gz ./

3. Restore in case of emergency

tar -xzvf backup-file.tar.gz
🌐 Connect your domain with free SSL

Step 1 β€” Set up the DNS

In your domain registrar's dashboard (Cloudflare, Namecheap, GoDaddy...), create a record:

Type
A
Name/Host
@ (root domain) or a subdomain, e.g. app
Content/Value
Your server's public IP

Wait 5 to 15 minutes for the record to propagate across the internet.

Step 2 β€” Automatic reverse proxy with Caddy

One single file, no Nginx config or manual certificates β€” Caddy issues and renews Let's Encrypt HTTPS on its own.

Create a file called Caddyfile:

yourdomain.com {
    reverse_proxy localhost:8000
}

Start Caddy with this command (pulls the image and runs it in the background):

docker run -d -p 80:80 -p 443:443 --name caddy --restart always -v $PWD/Caddyfile:/etc/caddy/Caddyfile -v caddy_data:/data caddy