Airbroke is a modern open source error catcher built on PostgreSQL with an HTTP collector compatible with Airbrake and Sentry endpoints. It offers a React-based frontend for error management, per-occurrence bookmarks, AI-assisted issue insights, and HTTP replay capabilities. The MCP API surface exposes the server as a runnable Node.js application that you can deploy in a Node-friendly environment or via Docker. After installation, you can build a production bundle and run the standalone server to serve the Next.js app. Use the API endpoints under /api for notices, envelopes, and related error data, and leverage the Replay and AI features to reproduce and triage issues quickly.

Prerequisites:

• Node.js 22/24+ installed on the target machine
• Git
• Yarn (or npm)
• PostgreSQL 15+ database

Install from source:

1. Clone the repository git clone https://github.com/icoretech/airbroke.git cd airbroke

2. Copy and customize environment variables cp .env.dist .env

   Edit .env to set DATABASE_URL, AUTH_SECRET, AIRBROKE_CORS_ORIGINS, etc.

3. Install dependencies and build yarn install yarn build

4. Run in production mode (standalone) after build yarn start

   Server will run the Next.js standalone app (default port 3000)

Docker option (if you prefer containers):

• Build the image docker build --no-cache -t icoretech/airbroke:latest .
• Run the image docker run -p 3000:3000 icoretech/airbroke:latest

Notes:

• Ensure DATABASE_URL is reachable from your server and the database allows connections from the host.
• After deploying, update AIRBROKE_CORS_ORIGINS to restrict origins in production.
• If deploying via Vercel/Render/Netlify, follow their deployment-specific env guidance and ensure database migrations run during boot or deploy as required.

Tips and common issues:

• AIRBROKE_CORS_ORIGINS should be restricted in production to your actual domains to prevent unauthorized access.
• If you encounter DB connection limits, consider using a connection pooler or Prisma Data Proxy.
• The Next.js app is served in standalone mode; ensure the .next/standalone/server.js path exists after a successful build.
• Migrations are typically executed during deployment on certain platforms; verify that Prisma migrations have run in your target environment.
• For local testing, you can run yarn start to serve on port 3000; adjust port mappings as needed in Docker/Kubernetes environments.