What LogBrew does

LogBrew groups errors into issues and links each one to the logs, trace, and release behind it. You can open that evidence in the dashboard, read it with the logbrew CLI, or let Claude, Cursor, or Codex read it over the hosted MCP server.

How it connects to your app

SDKs for 26 platforms send telemetry straight to the LogBrew API, with no local agent or collector to run. Each project has its own ingest keys, and a read key lets a coding agent or CI job read one project without signing in.

How your data is handled

You sign in with GitHub, GitLab, Bitbucket, or Google, so LogBrew stores no passwords. Each key is shown only once. Telemetry is kept for your plan's retention window, 30 days on Free, 90 on Pro, and 365 on Business, and deleted after it.

Read the Privacy Policy

Code you can read

The SDKs, the CLI, the MCP server, and the documentation are public on GitHub, so you can read the code that runs in your app.

LogBrew on GitHub

Start free

The Free plan needs no card, and new accounts get Pro free for 6 months.

See Pricing