Airbroke

Open Source Error Catcher

Features

Airbroke is currently in active development! Using it in production environments is at your own discretion. We appreciate your feedback and support as we work towards a stable release.

• :floppy_disk: Based on PostgreSQL
• :globe_with_meridians: Airbrake(tm)/Sentry(tm)-compatible HTTP collector endpoints
• :computer: Modern, React-based frontend for error management
• :rocket: Designed with simplicity at its core
• :wrench: Maintains small database footprint even under heavy data ingestion
• :robot: Ask AI about issues
• :clipboard: Provide cURL command to reproduce HTTP exceptions
• :arrow_forward: Replay HTTP exceptions
• :key: Supports multiple OAuth providers for secure user authentication
• :bar_chart: Occurrence charts
• :bookmark: Save and manage bookmarks for important occurrences
• :electric_plug: MCP API for LLM/agent integrations

System Requirements

• Node.js 22/24+ compatible environment
• Minimum of 300MB RAM
• At least 1000 millicores, equivalent to 1 CPU core
• PostgreSQL 15+ database
• 8+ free database connections slots per instance

Deployment Options

Airbroke provides flexibility in deployment options. You can either deploy it from the built source code or use a multiarch Docker image. For Kubernetes deployments, a Helm chart is provided. As Airbroke is a Next.js 16 application, it can be deployed wherever a Node.js server is supported. This includes managed environments such as Vercel, Netlify, and Heroku.

Build from source

For a production build, you can run:

cp .env.dist .env

Then edit the .env file to set your own values.

yarn install
yarn build

This will generate a .next build output. Because this repo uses output: "standalone", the runnable server output is in .next/standalone (see the Dockerfile for a working copy strategy / asset layout).

You can also run yarn start to test the production build locally on port 3000.

Docker

We publish images for both amd64 and arm64 architectures on ghcr.io but in case you want to build your own image you can do so.

You can build the Docker image with:

docker build --no-cache -t icoretech/airbroke:latest .

You can then run the image locally with:

docker run -p 3000:3000 icoretech/airbroke:latest

Vercel

While testing on Vercel has not been conducted, Airbroke should be fully compatible.

It's important to keep the following points in mind:

• For optimal performance, ensure your database is located in the same region.
• The endpoints under /api/* will be converted into serverless functions, which may introduce potential cold boot time.
• If you connect directly to Postgres, use a pooler (or Prisma Accelerate / Data Proxy) to avoid exhausting DB connections.
• Migrations must be executed as part of deployment. The Deploy Button above sets a build-command that runs DB migrations only for VERCEL_ENV=production before building (adjust this in your Vercel project settings if you need a different workflow).
• The Deploy Button defaults AIRBROKE_CORS_ORIGINS to * for quick starts. After your first deploy, set it to your deployed origin (for example https://.vercel.app) and any custom domains.