Bug reports from inside your app

Pro is $29 a month ($24 billed yearly) and Business $79 ($64 yearly). The Free plan is for trying it: 1 project, 10 reports and 500 error events a month, 7 days of history. It's a separate subscription from Testing, and you don't need a Testing plan.

Nothing is billed as overage. New reports or errors for that month are refused politely (the SDK waits and tries later), you get a notice at 80% and at 100%, and you can upgrade at any time with the difference prorated. Everything resets on the 1st.

Web apps through a JavaScript SDK with a built-in reporting widget (plain HTML, React, Next.js, Vue and others), and Flutter through a Dart package with a report sheet. Both can capture errors. Native iOS and Android apps, React Native and servers can send reports and errors through the HTTP API. The Flutter package isn't on pub.dev yet; the docs show how to add it.

Yes. The key is public by design: it can only send reports to its project, never read anything. Reads always need a signed-in Bugfed account. Rate limits, an optional list of allowed websites, an on/off switch and key rotation protect a project from abuse.

Nothing until someone sends a report. Then it sends what they typed, a screenshot only if they chose one, your app version and environment, the browser, OS, screen size and language, and the page address without its query string. It never reads the page, form fields, cookies, the console or network requests. IP addresses aren't stored.

Yes, if you turn it on in the SDK. Uncaught exceptions and failed promises (web), and Flutter and platform errors (Flutter), are grouped into issues with counts, installs affected and a trend per release. Reports and errors stay separate, and a report links to the errors its sender hit just before. Native crash signals such as iOS crashes and Android ANRs aren't captured yet.

It shows what happened, not why. With session tracking on, an issue page compares how often installs that hit it came back within a week with installs active the same days that didn't, and shows the sample sizes and ranges. It only calls a difference clear when the ranges don't overlap, and never says the error caused it.

Nothing unless the project owner turns them on. When someone asks for a summary, the project's recent report titles and descriptions, error titles and release numbers go to our AI provider's API (Google Gemini or Anthropic Claude, paid tiers that don't train on your data), without emails or user ids. Every point in the summary links to the reports and errors it's based on, and with too little data it declines to summarise.

Yes. Team members you've invited to your Bugfed account can read and triage every report: status, priority, duplicates and internal notes. Only the account owner can change project settings, rotate the key or delete a project.