Newest first · 14 releases
Changelog
What changed in Blipit, the browser SDK and the Odoo module. The Odoo module is on the Odoo Apps store for Odoo 19 and 18.
Connecting is one step and every mistake says why
- Save refuses anything but a secret key and explains where to get one.
- With a secret key and the agreement ticked, Save connects on its own and shows a Connected toast.
- A refused key (wrong, replaced, or already bound to another project) shows the reason at once and the Connect button stays usable.
- Field labels no longer clash with Google reCAPTCHA's Secret Key, which cleared a build warning on Odoo.sh.
Where to sign up, right where you need it
- Settings shows a link to create a free Blipit account until the database is connected.
- The empty Issues screen links to sign-up.
- The store listing names app.blipit.io/signup and says plainly that Odoo Online is not supported.
Agreement to the Terms and the licence on Connect
- Connect requires ticking agreement to the Blipit Terms of Service and the module licence; Blipit records who agreed and to which version.
- The agreement only counts once Blipit has accepted the key for that database.
Terms acceptance, API keys page, seats that mean one thing
- Everyone accepts the current Terms before using the dashboard; the version, time and address are kept, and a new version asks again.
- API keys has its own place in the sidebar: every project's public key and a button that creates a secret key.
- A seat is any person who receives alerts or uses the workspace: members, invites, email alert rules and Odoo people in charge share one count.
- Owners and admins can remove a project; the New project page shows plan limits up front with a link to plans.
- SMS and phone calls are hidden until they are set up; on-call steps that asked for them email instead.
Logs, tracing, session replay, on-call, releases, synthetic checks
- Logs: JSON, NDJSON and OpenTelemetry, with live tail and search.
- Tracing: Sentry transactions and OpenTelemetry traces, a Performance page, waterfalls and N+1 detection.
- Session replay with masked text and inputs, a player, and Watch replay on issues.
- On-call schedules, escalation policies and incidents with acknowledge links.
- Release health, deploys, suspect commits, code owners and user feedback.
- Uptime checks for SSL, domains, TCP, DNS and response time, with multi-region majority.
- Status pages, Jira, Linear and Microsoft Teams, snooze and sampling, two-factor sign-in and an audit log.
- MCP endpoint for Claude Code and Cursor; web vitals.
Browser SDK 0.2.0
- Web vitals, session tracking, a feedback dialog and the replay loader; about 7 KB gzipped.
Store listing and a seat-count fix
- New listing with real screenshots and a banner.
- A failed plan refresh no longer resets the seat count.
Pricing v3 and Sentry compatibility
- Free 100,000 events; Solo $9, Team $29, Scale $79 a month, or 2 months free yearly. Never billed per event.
- Any Sentry SDK reports to Blipit unchanged; uptime monitors and cron heartbeats; AI fix paid from prepaid credit.
Only Blipit users can trigger a sync
- Refresh from Blipit is limited to the Blipit group.
Proprietary licence, seats enforced by the server
- The module is licensed under the Odoo Proprietary License v1.0.
- People in charge are pushed to Blipit, which checks the seat count and sends the alert emails.
Multi-company and login monitoring
- Every error carries the company it happened in; issues show their companies; people in charge per company within the plan's seats.
- Login monitoring can be turned on: failed, blocked and successful sign-ins with IP and database, never the password.
First store listing
- Readable SDK build, store banner and a support contact.
Blipit as an Odoo app
- Issues are listed inside Odoo and synced every 10 minutes or on Refresh; resolve, ignore and reopen from Odoo.
- Regressions are marked when a fixed issue comes back; framework frames are told apart from custom code.
First release
- Unhandled Python exceptions and uncaught JavaScript errors reported to Blipit, bound to one database per key.