About Logister

Built for teams that want self-hosted error monitoring, not another closed tool.

Logister is an open source, forkable, self-hosted error monitoring and bug triage dashboard for your apps across Ruby, .NET, Python, JavaScript/TypeScript, and ColdFusion/CFML runtimes. We focus on helping teams see what changed, group repeated failures, preserve request context, assign ownership, and move from a production problem to a fix without bouncing between tools.

Logister overview dashboard showing cross-app event flow

Focus

Error ownership + release confidence

Approach

Open source, forkable, multi-runtime

Deploy

Registry releases, docs, hosted optional

Product in action

Designed for day-to-day triage flow across dashboards, inboxes, and insights.

Project inbox

Logister inbox detail view screenshot

Project insights

Logister insights timeline screenshot

Stability dashboard

Logister stability dashboard screenshot

Capture

Ingest errors, transactions, logs, metrics, and check-ins

One API shape, first-party Ruby, .NET, Python, and JavaScript packages, and one place to inspect reliability signals per project and release.

Triage

Group duplicate failures into an actionable inbox

Move issues through unresolved, resolved, ignored, and archived states with context preserved.

Operate

Self-host with infrastructure you control

The main path is to operate Logister yourself. The hosted app exists as an optional convenience, while the public source, release versions, GHCR and Docker Hub images, optional Quay mirrors, and runtime stack docs help teams plan their own deployment.

Operator details

Runtime and deployment details for teams self-hosting the app.

Runtime stack

  • Ruby on Rails + Puma
  • PostgreSQL (app data and event storage)
  • Redis + Sidekiq for background processing
  • Optional ClickHouse for analytics acceleration

Supported app integrations

  • logister-ruby for Rails and Ruby apps
  • logister-dotnet for ASP.NET Core and C# services
  • logister-python for FastAPI, Django, Flask, Celery, and Python services
  • logister-js for JavaScript and TypeScript apps, with optional Express middleware
  • Direct HTTP ingestion for Lucee and Adobe ColdFusion

Required production env

  • RAILS_MASTER_KEY
  • DATABASE_URL
  • REDIS_URL
  • LOGISTER_ADMIN_EMAILS

Optional integrations

  • Amazon SES for transactional email
  • Cloudflare Turnstile for auth protection
  • ClickHouse dual-write analytics path
  • Docker/Kamal deployment flows

Next step

Start with the self-hosted path, then connect real production services.