Brie vs Marker.io
Brie and Marker.io both turn a bug into a developer-ready report, a visual capture plus technical context, and create an issue in your tracker. Brie is a good fit for teams that want session replay, video, automatic in-browser redaction, multi-browser support, an open-source extension, and EU hosting. Marker.io may be the better choice if your team already uses it or wants its website feedback widget workflow.
What both tools do
Both tools let someone report a bug with the context developers need, a screenshot or recording with annotations, console logs, network activity, and environment details, and push it into an issue tracker so engineers can reproduce and fix it.
When Brie is a good fit
- You want session replay and video alongside console and network logs in one report.
- You want automatic in-browser redaction of tokens, keys, credentials, and financial data before reports are stored.
- Your team works across Chrome, Edge, Firefox, and Opera and wants one consistent extension.
- You prefer an open-source extension and EU hosting on Hetzner.
- You want reports to flow into GitHub, Linear, or Jira.
When Marker.io may be a better fit
- Your team already uses Marker.io and likes its workflow.
- You want an embedded website feedback widget for clients to report from your site.
- For Marker.io’s current capabilities and pricing, check marker.io directly, feature sets change.
Where Brie stands out
Session replay and video, not just annotated screenshots
Brie captures a session replay and video alongside console and network logs, so developers can watch what happened before the bug rather than working from a single annotated image.
Redaction before data leaves the browser
Brie redacts tokens, API keys, authorization headers, credentials, and financial data with [REDACTED_BY_BRIE] before a report is stored, and blocks recording on login and payment pages.
Open source and EU hosted
The Brie extension is open source on GitHub, and Brie runs on Hetzner infrastructure in the European Union with traffic encrypted in transit.