“It doesn’t work.”
No browser, no URL, no steps. The first hour goes to asking questions the reporter can’t answer.
Let your users show you the bug, not describe it.
Collect website feedback with annotated screenshots, browser context and session replay. Give your team the evidence available to reproduce bugs and track each report through resolution.
Free plan · No credit card · Works in any browser, mobile included
Collect screenshots, replay, logs and browser context for bug reports.
Evidence capture Bug reports with evidence
- Screenshot
- Replay
- Console
- Network
- Environment
Annotated page. The page route and browser context stay with the report.
Inputs always masked
Received → WIP → QA → Done renameable per project
The MCP server has 100% panel parity.
MCP server & docsHow likely are you to recommend us?
Surveys: NPS, CSAT, rating, choice, text
JSON theming on Free; custom CSS and whitelabel on Pro and Scale.
Every integration. Included on Free.
All integrations$0 no credit card
Pro $19/month Scale $99/month
Compare plans in detailThe bug report your team gets today
“Can you send a screenshot?”
Screenshots arrive cropped, three days later, of a page that already changed.
“Any update?”
The reporter never hears back, so they report it again, in another channel.
Install, capture, act. Three steps, one afternoon.
-
Paste one script tag
Styles stay in Shadow DOM. Capture scales back under host load.
Widget & host isolation -
Your users report with evidence
Annotated screenshot, replay, console, network and environment, attached automatically.
Evidence capture -
Your team finishes it on the board
Received → WIP → QA → Done. The reporter follows progress from a link, no account needed.
Board & pipeline
Watch what the user did before they wrote to you
When recording is available, session replay captures the lead-up to the report. Inputs are always masked, and the widget suspends itself when the host page is under load. The player says so instead of stitching over the gap.
Session replay
Beside the film runs the same session as a log: captured clicks, requests and console errors, in order. Click a line and the player seeks to it.
One reply, written once, in two places
Your team works the pipeline: Received → WIP → QA → Done, renameable per project, with severity and priority as separate fields. The reporter opens a link and reads the same answer.
Board & pipeline
Received → WIP → QA → Done, severity and priority apart.
Marked Visible to client, that reply leaves the board
Thanks Marta, we reproduced it and it is with engineering now. We will write here when it ships.
It appears on the reporter's own page and can reach their inbox when reply emails are enabled. Internal comments stay with your team.
The person who filed a bug follows their own reports from a link, without an account.
Reporter portal- No account, no password, no seat: the link is the credential and it expires in 30 days
- Every report they filed with you, and a reply box that answers back onto the ticket
- Your colours, your logo, five languages: it reads as your product, not as ours
Make it yours.
Keep your page first.
Design the feedback experience in a visual editor. Your colors, your words and your corners, with safeguards around your host page.
Explore the widgetStyle it visually.
Colors, radius and labels. Safe Theme validates what goes live.
Keep styles contained.
Scoped CSS stays inside the widget’s Shadow DOM boundary.
Give your page room.
Capture scales back under pressure. Written feedback remains.
Send it where the work
already happens.
Keep the context with the ticket. Keep your team in the loop.
Every integration. Included on Free. All integrations
Everything the panel does, your AI agent can do too
Notarus ships an MCP (Model Context Protocol) server with 100% panel parity. Ask your agent to investigate a report, follow the evidence and update the ticket, all in the same conversation.
MCP server & docsAn example conversation with an agent connected to the Notarus MCP server, about ticket NT-248.
- You
Why is checkout failing in NT-248?
- Agent
I'll read the report and follow the session evidence.
- Tool · get_ticket
{"ticket":"NT-248"}SPRING24 accepted · total $148.00 · screenshot + session attached
- Tool · get_session
{"session_id":"68d0a210-5997-493e-bfaf-f08d721ab318","limit_logs":50}Checkout · coupon applied → payment attempted twice
- Tool · search_logs
{"project_id":"c7c83980-5707-44ec-8d24-b54bb3b62b4e","session_id":"68d0a210-5997-493e-bfaf-f08d721ab318","query":"POST /api/pay","level":"network","limit":20}POST /api/pay → 500 POST /api/pay → 500
- Agent
The total stays at $148.00 after the coupon is accepted. Both payment attempts return 500. The failure is captured; the root cause still needs investigation.
- You
Move it to WIP and add an internal note with the evidence.
- Agent
I'll check the pipeline, move the ticket and leave the note for your team.
- Tool · list_ticket_statuses
{"project_id":"c7c83980-5707-44ec-8d24-b54bb3b62b4e"}Received → WIP → QA → Done · WIP key: wip
- Tool · move_ticket
{"ticket":"NT-248","status":"wip","position":"top"}NT-248: Received → WIP
- Tool · comment_ticket
{"ticket":"NT-248","visibility":"internal","body":"Coupon accepted; total remains $148.00. Two POST /api/pay requests returned 500. Root cause unconfirmed.","mentions":[]}Internal note saved · visible to your team
- Agent
NT-248 is in WIP. The evidence is saved as an internal note, ready for the team to investigate.
100%
panel parity
- list_tickets
- get_ticket
- create_ticket
- move_ticket
- assign_ticket
- comment_ticket
- list_sessions
- get_session
- get_recording
- search_logs
- get_errors
- list_ticket_statuses
- ticket_stats
- get_insights
- create_reporter_portal_link
- render_reply_template
An example conversation using Notarus tools. The agent reads the evidence, then moves the ticket and adds an
internal note when asked. get_documentation returns the full tool manual.
Built to be allowed on production
Six facts a security review asks about before a script goes on a production page, each with the artifact behind it rather than a promise.
-
Inputs always masked
Replay never records what users type. It is a property of the recorder, not a setting a project can turn off.
Inputs masked
-
Secrets scrubbed
Authorization, cookies and tokens stripped from captured logs. Request and response bodies are never read at all.
authorization: [scrubbed]
-
IPs salted-hashed
No raw IP is stored. Turn the capture off and nothing is stored in its place, not even a hash.
sha256(ip + salt), first 32 hex
-
Host isolation budget
Before every release, Notarus measures its own test pages with the widget against the same pages without it. These are the largest regressions that pass.
LCP p75 +50 ms · INP p75 +10 ms · CLS 0
-
The key in your page is not an account
It reaches the ingest endpoints and the widget's own configuration. It reads no ticket, no board and no account, and every ingest route is rate limited on its own.
data-key="pb_pub_…" · ingest only
-
Evidence expires, tickets do not
A nightly pass drops captured logs and performance data at 30 days and idle sessions at 90. Replay follows the project’s retention window, capped by its plan.
logs 30d · sessions 90d · replay capped by plan
Three plans, and the first one costs nothing.
Free
$0 /month
No credit card
Covers 5 projects with session replay, screen recording and every integration, and every plan has unlimited seats.
- Seats
- unlimited seats
- Projects
- 5 projects
- Page views
- 100,000 page views a month
- Storage
- 10 GiB
- Replay retention
- 30-day replay retention
Pro
14-day trial $19 /month $190 /year
$190 billed yearly · save $38 $15.83 a month · save $38
Pro takes the badge off the widget and adds review mode and weekly AI insights.
- Seats
- unlimited seats
- Projects
- 20 projects
- Page views
- 500,000 page views a month
- Storage
- 50 GiB
- Replay retention
- 90-day replay retention
Scale
14-day trial $99 /month $990 /year
$990 billed yearly · save $198 $82.50 a month · save $198
Scale adds SAML sign-on, audit log export and masking rules of your own.
- Seats
- unlimited seats
- Projects
- unlimited projects
- Page views
- 2,000,000 page views a month
- Storage
- 250 GiB
- Replay retention
- 180-day replay retention
Make the next report the start of a fix.
Bring feedback, screenshots, and the next step together in Notarus.
Questions teams ask before installing
Does the widget slow down my site?
The widget loads asynchronously and isolates its styles with Shadow DOM. Its Host Isolation Contract limits CPU, memory, network traffic and rendering work. When the page is under pressure, it reduces or suspends evidence capture while keeping written feedback available. These limits do not guarantee that your site's performance metrics will never change.
What does a report include on the Free plan?
Free includes annotated screenshots, session replay, screen recording and browser context, plus surveys and the reporter portal. What reaches a ticket depends on the reporter’s choices, capture settings, browser support and available performance and plan budgets. Written feedback can still be sent when evidence is unavailable.
Is session replay safe for pages with personal data?
Inputs are always masked, so replay never records what users type. Authorization headers, cookies, passwords, tokens and secrets are scrubbed from captured logs, request and response bodies are never captured, and IP addresses are stored salted-hashed.
Can I use Notarus without the panel, only through MCP?
Yes. The MCP server has 100% panel parity: every capability of the panel has a tool. Point your agent at POST /mcp with a personal access token and it can triage, reply, move tickets and open review sessions.
Which browsers are supported?
Chromium, WebKit and Firefox, on desktop and mobile. The cross-browser matrix is a gate that runs before every deploy, not a claim.
Start free Free plan · No credit card