Every bug, replayed.Less guesswork. Faster fixes.
Web Scout brings the user's journey, console logs and failed requests into one timeline — so developers can find the cause and support can share the context. No dashboards full of distractions.
By Rubicon Microproducts · Recording on your terms
What you get
Precise DOM & click capture
Mutation-level DOM diffs and exact click targets with selectors — not blurry video.
Console logs, synced
Every log, warn and error pinned to the replay timeline. Click a line, jump to the moment.
Network waterfall
Method, status, timing and size for every request. Failed calls light up on the scrubber.
Stack traces → GitHub
One click packages repro URL, env, steps and errors into a ready-to-file GitHub issue.
Zero bloat
No heatmaps, no funnels, no ad pixels. Capture authorization stays under your control.
Privacy-conscious
Configure capture scope and sampling for your project. Keep sensitive data out of your recordings.
Built for the people who fix things
One replay view, three very different headaches solved.
For developers
Stop reproducing bugs by email.
- Replay the exact session — DOM, clicks, console and network in one timeline.
- See the stack trace, the failed request and the user's path in the same view.
- File a GitHub issue with repro steps, environment and errors in one click.
- No more “works on my machine” — you watch it break, then fix it.
For support teams
See what your users saw.
- Stop asking “can you send a screenshot?” — replay the session instead.
- Filter sessions by URL, errors, or time range and find the bad ones in seconds.
- Hand developers a link with full technical context already attached.
- Resolve tickets on the first reply instead of the fifth.
For engineering leads
Give your team the full picture.
- Give developers and support a shared view of what went wrong.
- Keep investigations focused with the session, errors and requests together.
- Recordings are stored in Canada (Azure Canada Central).
- Role-based access: admins, developers and viewers see exactly what they should.
Why teams pick Web Scout
The big platforms are built for analytics or company-wide monitoring. Web Scout does one job — helping you find and fix the bug — and does it without the overhead.
They focus on: marketing analytics — heatmaps, scroll depth and behaviour insights, funded by a large ad and data ecosystem.
Web Scout: a developer view: console logs, failed requests and stack traces synced to the replay, with recordings stored in Canada.
They focus on: recording every session continuously, with product analytics and pricing tied to session volume.
Web Scout: recording when you need it. Pause capture instantly and only pay for days you actually record.
They focus on: company-wide monitoring with many add-on products, where replay is one more line on a large bill.
Web Scout: a focused debugging tool your team can adopt in minutes, without an observability contract.
They focus on: dashboards and metrics for infrastructure — great for seeing that something broke, not what the user did.
Web Scout: the exact user journey behind the error, ready to hand to a developer or file as a GitHub issue.
| Comparison | Web Scout | Typical analytics replay | Typical full observability suite |
|---|---|---|---|
| Main purpose | Find and fix bugs | Marketing & product insight | Infrastructure monitoring |
| Console + network synced to replay | Built in | Limited or none | Often a paid add-on |
| Pause recording instantly | One switch | Rarely | Config change |
| Pricing | Active days you record | Free (ad-funded) or per session | Per session / per host |
| Choose where data lives | Canada (Azure Canada Central) | Vendor's region | Limited regions |
| Heatmaps, funnels, ad pixels | None — less to secure | Core features | Optional |
General comparison of product categories. Product names are trademarks of their respective owners.
Quick answers
When Web Scout is the better fit — and when it isn't.
When is Web Scout a better fit than Microsoft Clarity?
When the job is debugging, not analysing. Clarity answers where users click; Web Scout answers why the page broke — console output, the failing request and the stack trace, in the same replay, with recordings stored in Canada.
Why choose it over LogRocket or FullStory?
If recording every session continuously is more than you need. Switch capture on for the days you're hunting a bug and pause it the moment you're done, without carrying a product-analytics suite you'd rarely open.
We already run Datadog. Do we need this?
Keep Datadog for infrastructure. Web Scout covers the other half: the exact session behind the alert, replayable and shareable, so a developer or support agent can pick up the story without another query language.
Isn't Grafana enough?
Grafana tells you something broke. Web Scout shows what the user did while it broke — clicks, console lines, network timing — then packages that context into a GitHub issue.
When should we not use Web Scout?
If you need heatmaps, funnels or marketing attribution, an analytics tool is the better fit. Web Scout is deliberately narrow: finding and fixing bugs.
From capture to fix in three steps
Drop in the capture snippet
Your framework checks recording authorization with one API call before it captures anything.
Replay real sessions
Timeline player with synchronized console, network waterfall and DOM inspector — nothing else.
Ship the fix
Package repro context into a GitHub issue, fix the bug, flip capture back off.
Capture on your terms.
Turn recording on when you need context, and pause it when you don't. Your script checks authorization before capturing, keeping you in control of what gets recorded. Flexible active-day pricing follows the same rhythm.
Explore plans →{
"authorized": false,
"paused": true,
"reason": "paused",
"billing_mode": "prepaid",
"remaining_days": 12
}Your data stays where you put it
Recordings are stored in Canada (Azure Canada Central).
PII stays in Canada
Session data — DOM changes, clicks, console messages, network metadata and any personal information it contains — is stored and processed in Azure Canada Central.
Keep sensitive data out at the source
Error-only capture, configurable sampling and capture scope let you exclude personal and sensitive fields before anything is ever recorded.
Encrypted in transit and at rest
Everything your capture script sends travels over encrypted connections, and recordings are stored encrypted in Canada.
No ad networks. No resale.
We do not sell session data, share it with advertising or analytics brokers, or use it for anything other than helping your team debug.
Access you control
Role-based team permissions decide who can view sessions and change capture settings. API keys are stored only as hashes and can be revoked instantly.
Deletion on request
Your data belongs to you. Ask us to delete your recordings and account data and we will, subject only to legal obligations.
Data residency and privacy details are covered in our Privacy Policy and Terms of Service.