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, purpose-based project notifications, assignment, and self-hosted delivery.
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.
Evaluation path
Use each use case as a short decision checklist.
- Pick the page that matches the job: replacing a hosted tool, running the stack, routing notifications, or instrumenting one runtime.
- Open the linked setup guide and complete the smallest realistic path, usually one project and one representative event.
- Verify the result in Logister: inbox grouping, detail context, assignment, status, notification delivery, or deployment health.
- Use the troubleshooting links on the setup page before expanding to more services or optional infrastructure.
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 project notifications
Send Logister project email through Rails SMTP settings backed by SES or another provider.
Integration paths
Pick the project type that matches the surface you are instrumenting.
Use-case pages explain the evaluation path when teams commonly search by runtime. Integration guides are the canonical setup path for every supported project type, including mobile apps, Cloudflare Pages sites, and custom HTTP clients.
Ruby
Ruby and Rails apps
Use logister-ruby for Rails exceptions, manual Ruby events, logs, metrics, transactions, spans, check-ins, DB timing, source context, and deployment records.
Python
Python APIs and workers
Use Logister with FastAPI, Django, Flask, Celery, workers, schedulers, Python logging, source context, deployments, and custom telemetry.
.NET
ASP.NET Core and C# services
Use Logister with request exceptions, service errors, transactions, spans, custom metrics, logs, check-ins, source context, and deployment records.
JavaScript
JavaScript and TypeScript
Use Logister with Node, Express, browser timing, TypeScript services, workers, console capture, metrics, spans, and scheduled check-ins.
Android
Android apps
Use the Kotlin-first Android SDK from Maven Central for app-controlled errors, logs, metrics, transactions, spans, check-ins, release metadata, and safe device context.
iOS
iOS apps
Use the Swift Package Manager integration for async iOS app telemetry, including errors, logs, metrics, transactions, spans, check-ins, source context, and CI deployment records.
CFML
Lucee and Adobe ColdFusion
Use direct HTTP ingestion from CFML apps to send structured errors, request context, logs, metrics, and custom telemetry into Logister.
Cloudflare
Cloudflare Pages sites
Create a Cloudflare Pages project when the monitored surface is a Pages site, then send deployment, traffic, log, metric, and check-in signals through the HTTP API.
Custom
Manual / HTTP API clients
Use the generic HTTP API project type for custom clients, scripts, Workers, unsupported runtimes, deployment records, check-ins, and one-off operational telemetry.