Every error,
with the context to fix it
A stack trace tells you where it broke. LaraBug sends the request, the query that ran, the job that dispatched it and the user it happened to, so the first thing you read is the whole story rather than the last line of it.
✔︎ 14-day free trial ✔︎ No credit card required
Grouped, not repeated
The same exception from a thousand requests is one issue with a thousand occurrences, counted and charted by the day. It is fingerprinted on the class, the file and the line, so a deploy that shifts the trace does not split it in two, and an issue you marked fixed that comes back reopens itself.
Issues · Unfixed
-
TP 1,204
SQLSTATE[40001]: Deadlock found when trying to get lock
Laravel StockReserver.php • 2 minutes ago
-
JL 642
Cannot read properties of undefined (reading 'price')
JavaScript ProductCard.js • 6 minutes ago
-
318
Undefined array key "variant_id"
Livewire Cart.php • 14 minutes ago
-
AR 57
Call to a member function format() on null
Laravel InvoicePdf.php • 1 hour ago
The whole request, not just the trace
Every occurrence carries the route, the payload, the headers and the session, and the user it happened to with the release they were on. The keys you name are filtered before they leave your server, and the source sits beside the trace with the failing line marked.
Owned and discussed by your team
Your team works out the cause in the thread, gives it an owner and a priority from the panel, the app or an MCP client, and shares a link with anyone outside the team, revoked when you are done. Every change lands on the issue's trail, so the whole team sees who has it.
Everything that opens an issue
- Exceptions Everything the exception handler reports, with its request.
- JavaScript errors From the browser, Vue, React and Inertia, mapped back to source.
- Deprecations Each deprecated call, grouped per line of code.
- Regressions A fixed issue that comes back reopens itself.
- Logged errors Errors written to the log without an exception.
- CVE findings A vulnerable package in your lockfiles, in the same list.
- Teams and assignees Invite your team with a role each, and hand every issue to a teammate at the priority it deserves.
- Public links Share one issue with someone outside your team, and revoke it.
Keep reading
- Vulnerability scanning (CVE) The CVE in a package you did not know you had Known CVEs in your dependencies, with the fix version. Explore
- Alerts and integrations The right alert, in the right channel Slack, Discord, Teams, webhooks and email. Explore
- AI and MCP Your agent can read your errors Let Claude or Cursor read your issues. Explore
Catch the next bug before your users do
Nathan marked it fixedTwo minutes to install, a free plan that stays free, and your data kept in the EU. Teams have trusted LaraBug with their Laravel errors since 2016.