Airbroke logo

Airbroke

Lightweight PostgreSQL‑backed error catcher with Airbrake‑compatible API

Airbroke offers a modern React/Next.js UI and an Airbrake‑compatible HTTP collector, storing errors in PostgreSQL with a tiny footprint, and supports Docker, Helm, and serverless deployments.

Airbroke banner

Overview

Highlights

Airbrake‑compatible HTTP collector endpoint
Modern React/Next.js UI with charts and bookmarks
Small PostgreSQL footprint under heavy ingestion
Multiple OAuth providers and AI‑assisted issue analysis

Pros

  • Minimal database resource usage
  • Flexible deployment options (Docker, Helm, serverless)
  • Rich, modern UI for error exploration
  • Extensible authentication and AI assistance

Considerations

  • Still in active development; not officially production‑ready
  • Requires PostgreSQL 15+ and minimum system resources
  • Serverless deployments may suffer cold starts and need a data proxy
  • Documentation for some platforms (e.g., Vercel) is limited

Managed products teams compare with

When teams consider Airbroke, these hosted platforms usually appear on the same shortlist.

Airbrake logo

Airbrake

Error monitoring platform for tracking application exceptions and performance issues

Bugsnag logo

Bugsnag

Full-stack error monitoring and application stability management platform for proactive bug detection

Rollbar logo

Rollbar

Real-time error monitoring and tracking

Looking for a hosted option? These are the services engineering teams benchmark against before choosing open source.

Fit guide

Great for

  • Teams needing an Airbrake‑compatible collector without vendor lock‑in
  • Developers who prefer self‑hosted PostgreSQL storage
  • Organizations using Kubernetes or Docker Compose for services
  • Projects that want AI‑driven error analysis

Not ideal when

  • Mission‑critical production environments before a stable release
  • Teams lacking PostgreSQL expertise or infrastructure
  • Pure serverless workloads sensitive to cold‑start latency
  • Users requiring out‑of‑the‑box multi‑region scaling

How teams use it

Integrate legacy Airbrake clients

Collect and view errors through Airbroke UI without code changes

AI‑driven debugging

Ask built‑in AI to explain root cause and receive reproducible cURL commands

Kubernetes deployment with Helm

Deploy a scalable error service alongside pgBouncer via GitOps

Docker Compose local development

Spin up the full stack quickly for testing and debugging

Tech snapshot

TypeScript97%
PLpgSQL1%
Jsonnet1%
Shell1%
Dockerfile1%
JavaScript1%

Tags

monitorerror-monitoringerror-handlingcrash-reportspostgresqlerror-loggingnextjsmonitoringdevopscrash-reportingsentrycrash-reporting-toolairbrake

Frequently asked questions

Is Airbroke production ready?

It is currently in active development; use it in production at your own discretion.

Which database does Airbroke require?

PostgreSQL 15+ with at least 8 free connection slots per instance.

Can I deploy Airbroke to serverless platforms like Vercel?

Yes, but be aware of potential cold starts and the need for a data proxy for database connections.

How are users authenticated?

Airbroke supports multiple OAuth providers configured via environment variables.

Are Docker images available?

Multi‑arch images for amd64 and arm64 are published on ghcr.io.

Project at a glance

Active
Stars
197
Watchers
197
Forks
8
LicenseMIT
Repo age2 years old
Last commit3 days ago
Primary languageTypeScript

Last synced 2 days ago