When Logister fits
Choose Logister when self-hosting and team triage are the priority.
Logister focuses on grouped application errors, assignment, request context, occurrence history, related logs, project notification preferences, and active or archived project workflows in a Rails app your team can run and modify.
Comparison
What Logister emphasizes.
| Need | Logister approach |
|---|---|
| Own the deployment | Run the Rails app, worker, PostgreSQL, Redis, optional S3 archive storage, and optional ClickHouse in your infrastructure. |
| Track releases | Use release metadata in incoming events and versioned GHCR or Docker Hub images, plus optional Quay mirrors when configured, for the app itself. |
| Assign work | Filter by assigned-to-me, unassigned, teammate, status, and project. |
| Support multiple runtimes | Connect Ruby, .NET, Python, JavaScript/TypeScript, Android, iOS, CFML, or direct HTTP integrations. |
| Fork and adapt | Use the MIT-licensed code while replacing Logister branding in public forks or redistributed versions. |
Next steps
Evaluate by running one project end to end.
- Start a self-hosted instance with a web process, worker, PostgreSQL, Redis, and SMTP configured.
- Create one project and connect the runtime your team uses most often.
- Send one production-like event with environment, release, request context, and stacktrace data.
- Assign the grouped issue, change its status, and inspect whether the detail view gives enough context to act.
- Review notification and retention settings only after the first event path works.