Why these pages exist
Different teams discover Logister through different jobs.
Some teams search for a self-hosted monitoring stack. Some are comparing paid error tools. Others already have a bug tracker but want production error context, assignment, and release history in one place. These pages describe those paths directly and link back to the canonical setup docs.
Self-hosting
Self-hosted error monitoring
Run Logister yourself with Rails, PostgreSQL, Redis, Sidekiq, SMTP/Amazon SES, optional S3 archive storage, optional ClickHouse, and versioned registry images.
Comparison
Sentry alternative
Use Logister when your team wants open source code, Docker-based releases, and grouped issue triage in your own infrastructure.
Comparison
Bugsnag alternative
Use Logister when you want error grouping, first-occurrence alerts, assignment, and digest workflows without a hosted-only dependency.
Comparison
Bugzilla alternative for app errors
Use Logister when bugs start as production exceptions and need request context, occurrences, owners, and status workflows.
Important note
Comparison pages are descriptive, not affiliation claims.
Logister is independent and is not affiliated with Sentry, Bugsnag, Bugzilla, or their maintainers. The comparisons explain when Logister's open source, self-hosted operating model may fit teams evaluating those categories of tools.
Operations and team workflows
Use these pages when the question is how Logister runs day to day.
Self-hosting
Docker registry self-hosting
Run the versioned release image with separate Rails web and Sidekiq worker containers, PostgreSQL, Redis, SMTP, optional S3 archive storage, and optional ClickHouse.
Team workflow
Error assignment and team triage
Assign grouped errors to project teammates, filter inboxes by owner, and connect production context to Bugzilla-style ownership.
Notifications
Amazon SES alert emails and digests
Send first-occurrence alerts and daily or weekly digest summaries through Rails SMTP settings backed by SES or another provider.
Runtime-specific monitoring
Pick the page that matches the stack you are instrumenting.
Ruby
Rails error monitoring
Use Logister with logister-ruby to capture Rails exceptions, request context, assignment, and related logs.
Python
Python error monitoring
Use Logister with FastAPI, Django, Flask, Celery, workers, schedulers, and Python logging.
.NET
ASP.NET Core error monitoring
Use Logister with .NET services, request details, transactions, spans, custom metrics, and scheduled check-ins.
JavaScript
JavaScript and TypeScript monitoring
Use Logister with Node, Express, TypeScript, workers, and console or structured logs.
CFML
ColdFusion error monitoring
Use direct HTTP ingestion from Lucee or Adobe ColdFusion apps and keep grouped issue ownership in Logister.