LogisterDocumentationBugsnag alternative
Open source Bugsnag alternative

Use Logister for grouped errors, ownership, and useful notification cadences.

Logister is independent and is not affiliated with Bugsnag. This page is for teams that want error grouping, assignment, and notification controls in a self-hosted app rather than a closed hosted-only workflow.

When Logister fits

Choose Logister when alerts need to become owned work.

Logister groups repeated exceptions into issue-like error groups, then lets teams assign owners, filter inboxes by assignment, mark issues fixed, ignore noise, archive historical work, and inspect request context before deciding what to do.

Notifications

Keep email tied to intent.

Project notification preferences are split into purpose-based paths for error triage, project health, workflow routing, digest summaries, delivery controls, and operational notices. Self-hosted installs use standard Rails SMTP settings, commonly backed by Amazon SES, and Sidekiq sends mail outside the web request.

Read notification docs.

Operations

Run releases from your own infrastructure path.

Versioned Docker images are built once, verified through public GHCR, Docker Hub, and optional Quay references, and then promoted to Fly by immutable digest. Self-hosters can pin a version such as ghcr.io/taimoorq/logister:v3.5 or docker.io/taimoorq/logister:v3.5, use latest, or build from source.

Read the Docker self-hosting guide.

Fit check

Logister works best when email supports triage instead of replacing it.

Choose Logister when project users can review grouped issues in the inbox and use mail as a prompt, digest, or routing layer. If your only requirement is high-volume alert fan-out without a shared product workflow, tune your incident-management or paging stack separately.

Evaluate

Check grouping, ownership, and mail before comparing feature lists.

  1. Send two similar exceptions from the same runtime and confirm they group into one issue.
  2. Assign the grouped issue, filter the inbox by owner, and change the issue status.
  3. Enable one error triage notification and one digest for a project user.
  4. Trigger a test event and confirm Sidekiq delivers the expected email through SMTP or SES.
  5. Pin one Docker image tag in the deployment plan so the evaluation matches a repeatable release.