Bugsink Hosting

Track application errors and exceptions with a focused, self-hosted issue dashboard.

Order now No setup fees
  • One click deploy
  • 1 GB RAM Memory needed
  • 15 GB Disk Space Needed
  • From 2 € Price

Tech

Docker image
bugsink/bugsink:latest
Default port
8000
Database
postgres

How Bugsink works

Applications send exceptions to Bugsink through compatible Sentry SDKs. Each project receives a DSN, and the SDK attaches error details such as stack traces, code context, environment, release, tags, and available local variables. Bugsink groups similar events into issues so repeated failures can be reviewed as one problem rather than hundreds of separate entries.

Developers open an issue to inspect occurrences, understand affected releases or environments, and move it through a resolution workflow. Source maps and release information can improve JavaScript diagnostics when configured correctly. The service focuses on receiving and presenting error events rather than replacing application logs, metrics, or full performance tracing.

Key Bugsink features

Compatibility with Sentry SDKs makes migration possible by changing the DSN instead of replacing instrumentation libraries. Stacktrace-first views put the exception and surrounding context near the centre of the investigation. Issue grouping reduces noise, while search and tags help narrow failures by project, environment, release, or user context.

Alerts can notify a team upstream, but application email is disabled in this catalogue deployment, so email alerts do not leave the hosted installation. Developers should rely on the Bugsink dashboard and any separately validated integration rather than assuming email notification coverage.

Bugsink vs Sentry

Bugsink is a focused self-hosted error tracker built around Sentry SDK compatibility, grouped issues, stack traces, and a comparatively small operational footprint. Sentry is a broader commercial monitoring platform that combines error tracking with performance traces, logs, session replay, profiling, and provider-operated services.

Sentry may suit organisations that want a wider observability product and managed service options. Bugsink is attractive when the requirement is dependable crash reporting with familiar SDKs and direct control of stored error data, without operating a full monitoring platform.

Who uses Bugsink

Application developers use Bugsink to collect production exceptions from web services, background jobs, and client applications. Agencies can separate projects by customer, while small engineering teams use release and environment tags to distinguish current failures from older deployments.

Error reports may contain personal data, request details, or local variables. Teams should review SDK scrubbing settings and avoid capturing secrets, authentication tokens, payment data, or other sensitive values that are not needed for diagnosis.

Self-hosting Bugsink: requirements and cost

Resource demand grows with event volume, stacktrace size, issue grouping, retention, search, source maps, release activity, and concurrent reviewers. PostgreSQL stores projects, issues, occurrences, users, and configuration. The database is included but unmanaged, and its memory is outside the exported Bugsink application minimum.

AvaHost maps Bugsink to Plan 2 at €5 after the database adjustment. The service includes one-click deployment, a custom error-tracking domain, automated HTTPS, automatic application updates, and scheduled backups. Application email is disabled, so email alerts and email-based recovery are unavailable; teams should monitor the dashboard and preserve administrator credentials.

F.A.Q

  • Bugsink starts at €5 on Plan 2 after adding headroom for PostgreSQL. The plan covers event ingestion, issue grouping, stacktrace storage, search, and normal team review. Event volume, payload size, source maps, retention, project count, and simultaneous users determine whether a larger plan is needed.

  • PostgreSQL holds projects, users, DSN configuration, issues, error occurrences, tags, releases, and related application state. AvaHost provisions the database and connects it to Bugsink, but the service remains unmanaged. Database data should be protected together with any persistent application assets during updates, migration, or recovery.

  • Bugsink is designed to accept events from Sentry-compatible SDKs. Each project provides a DSN that replaces the previous event destination in the application configuration. A custom domain with automated HTTPS can protect that endpoint. Test one non-sensitive exception first and review SDK data-scrubbing settings before enabling production traffic.

  • Application email delivery is disabled, so Bugsink cannot send email alerts or password-recovery messages from the hosted installation. Error ingestion, grouping, stacktrace review, search, and issue management remain available in the browser. Teams should establish a dashboard-review routine and validate any non-email notification path before relying on it.