LogBrew connects to your existing tools through OAuth. Tap Add Project, choose an integration, complete the OAuth flow, and LogBrew handles the rest. Webhook registration, token management, and event normalization all happen automatically in the background. Each integration maps to one or more LogBrew projects. A project is the unit you receive notifications for and browse in your event feed. Some integrations (Linear, Railway) create exactly one project per connection; others (Vercel, Sentry, PostHog) let you select which of your provider projects to monitor and create a corresponding LogBrew project for each.Documentation Index
Fetch the complete documentation index at: https://docs.logbrew.co/llms.txt
Use this file to discover all available pages before exploring further.
Supported integrations
Sentry
Real-time error alerts, crash reports, issue SLA notifications, and two-way resolve sync with your Sentry organization.
Vercel
Deployment status events and live build, edge, and lambda log streaming from your Vercel projects.
Railway
Deployment lifecycle events plus real-time deployment and build logs streamed directly from your Railway services.
PostHog
Exception tracking and product error logs from your PostHog projects, with resolve sync via suppression state.
Linear
Issue SLA breach and high-risk alerts from your Linear workspace, with two-way resolve sync.
Stripe
Payment failure alerts, dispute notifications, subscription lifecycle events, and refund tracking from your Stripe account.
How connections work
Every integration follows the same pattern:- OAuth only. You authorize LogBrew through your provider’s official OAuth flow. No API keys to copy, no secrets to store on your device.
- Automatic webhook registration. Where applicable, LogBrew registers the necessary webhooks with your provider immediately after you connect. You don’t need to configure anything in your provider’s dashboard.
- Token management. LogBrew refreshes OAuth tokens automatically in the background. Your connection stays active without any manual re-authorization.
- Soft disconnect. When you remove an integration, LogBrew cleans up the associated webhooks and log drains from your provider automatically.
Severity levels
All events in LogBrew carry one of three severity levels:| Level | Color | Meaning |
|---|---|---|
| Critical | Red | Requires immediate attention: errors, failures, SLA breaches, payment failures |
| Warning | Yellow | Degraded state: canceled deployments, SLA at risk |
| Info | Blue | Informational: successful deployments, subscription updates |