Open source error monitoring and bug triage

An open source alternative for teams who want to self-host error monitoring.

Logister is an open source, self-hosted error monitoring and bug triage app for teams that want a forkable alternative to Bugsnag, Sentry, and Bugzilla-style workflows. Run it yourself, pull versioned Docker images from GHCR or Docker Hub, and keep errors, transactions, logs, metrics, and check-ins in infrastructure you control.

Open source Forkable Versioned registry images Self-host first Ruby, .NET, Python, JS, and CFML
Logister overview dashboard on desktop

Real product screenshots

Logister overview dashboard on desktop
Logister projects index on desktop
Logister project inbox and triage detail on desktop

Median triage time cut

72%

from first alert to assigned owner

Signal retention

99.9%

stacktrace, context, trace and request IDs

Time to first event

5 min

install a package, generate key, ship

Inbox

Bug tracking and error grouping in one queue

Use one inbox for unresolved, resolved, ignored, and archived issues, with owner assignment and occurrence history built around engineering triage.

Context

Trace-linked detail with stacktrace and related logs

Pivot from an exception to nearby logs and transaction traces without switching tools or tabs.

Self-hosting

Docs, releases, and Docker images for operators

Use public docs, explicit environment references, Docker self-hosting paths, and versioned GHCR or Docker Hub images instead of piecing together a private deployment recipe.

Why teams choose Logister

Built for teams that want ownership, not another closed SaaS dependency.

01

Forkable source

Run the public Rails app as-is, inspect the implementation, or fork it when your team needs different operational defaults.

02

Versioned releases

Self-hosters can track GitHub Releases and pull matching Docker images from GitHub Container Registry or Docker Hub.

03

Documented operations

Deployment, environment variables, SES email, Redis jobs, PostgreSQL, optional ClickHouse, and SDK setup are documented for repeatable installs.

How it works

Three steps from setup to calmer on-call rotations

01

Create project + key

Create a project, mint a key, and send your first event from production or staging.

02

Choose your integration

Use logister-ruby, logister-dotnet, logister-python, logister-js, or direct CFML HTTP ingestion to capture errors, logs, metrics, and check-ins with minimal setup.

03

Triage with confidence

Group duplicates, confirm regressions per release, and drive fixes from a single inbox.

Install in minutes

bundle add logister-ruby
dotnet add package Logister.AspNetCore
pip install logister-python
npm install logister-js
LOGISTER_API_KEY=your_key_here

Run it yourself

Self-host Logister and keep clearer error ownership close to your team.