Self-hosted error monitoring

Self-host error monitoring and bug triage with Logister.

Logister gives teams a forkable Rails app for grouped production errors, ownership, and runtime telemetry. Run it with PostgreSQL, Redis, and Sidekiq, connect Ruby, .NET, Python, JavaScript, Android, iOS, CFML, Cloudflare Pages, or direct HTTP clients, then inspect what arrives from the web UI or CLI.

Open source Forkable Versioned registry images CLI read tools Self-host first Ruby, .NET, Python, JS, Android, iOS, and CFML

Real product screenshots

Signal families

6

errors, logs, metrics, transactions, spans, check-ins

Integration paths

9

SDK, mobile, Cloudflare Pages, CFML, and HTTP options

Required app processes

2

Rails web plus Sidekiq worker

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, versioned GHCR and Docker Hub images, and optional Quay mirrors 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, SDK setup, and CLI read workflows are documented for repeatable installs.

How it works

Three steps from setup to owned triage

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, spans, and check-ins with minimal setup.

03

Triage with confidence

Group duplicates, confirm regressions per release, inspect issue context from the CLI, and drive fixes from a single inbox.

Connect and inspect

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

npm install -g logister-cli
logister auth login --host https://logister.example.com

FAQ

Can Logister be self-hosted?

Yes. The documented baseline is a Rails web process, a Sidekiq worker, PostgreSQL, and Redis. SMTP, ClickHouse, S3-compatible archives, Turnstile, and analytics are optional.

FAQ

What does Logister collect?

Logister stores application errors, logs, metrics, transactions, spans, and check-ins, then turns repeated failures into grouped issues that can be assigned and reviewed.

FAQ

Is the hosted app required?

No. The hosted app is optional. The primary product path is open source and self-hosted, with public source, Docker images, and deployment documentation.

Run it yourself

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