Releases
Know whether the release you just shipped is healthy.
Adoption, crash-free sessions, deploys and the commits most likely behind a new error, for every release.
Every plan, Free included
Explore ReleasesLive data on pull requests
See the errors behind a change before you merge it.
One comment on each GitHub pull request with the open errors, and in Odoo the slow queries, behind the lines it changes.
What it does
- 01
Matched exactly through stack traces, so it uses no AI credit.
- 02
The comment updates on every new commit.
- 03
Only changed file names and line numbers are read; no code is sent anywhere.
- Plan
- Scale plan
- Works with
- Every stack
Up next
Keep exploring Blipit.
Bug reports
Your users show you the bug. Blipit shows you the code.
A Report a bug button that sends a marked-up screenshot or a screen recording with voice, with the browser, page and errors attached.
Every plan, Free included
Explore Bug reportsService desk
Answer every report, and keep the reporter in the loop.
Reply to the reporter by email or in the Odoo chatter, talk with your team in internal notes, and attach the files that explain the fix.
Every plan, Free included
Explore Service deskYour next bug is already on its way.
Start on the Free plan. Add the SDK, the report button or the Odoo module, and your next bug arrives with the code that broke.