AnchorMark
Start free
Context

Repro steps that engineers actually act on.

AnchorMark records the page, the console, the failed requests, and the environment so the bug never has to be re-described.

See pricing
Problem

Why this hurts today

"Cannot reproduce" is the most expensive label in your tracker. Reproductions die when the reporter forgets a tab they had open, can't remember the browser they used, or gets logged out before they can come back to grab a screenshot. Engineers spend their day chasing context that no longer exists.

Solution

What AnchorMark does

Our SDK captures the last 50 console events, recent failed network calls, the rendered DOM snapshot, and a browser/OS fingerprint. Engineers open a ticket already loaded with everything they need. Sensitive data is redacted on capture, the SDK is under 30 KB gzipped, and the buffer is idle until a reviewer opens the widget — so production performance stays untouched.

Capabilities

What you get when you turn this on.

Screenshot + redaction

Full-page or viewport captures, with auto-blurring for inputs marked sensitive.

Console and network

Buffered logs and failed XHR/fetch responses, with PII scrubbing rules.

Environment fingerprint

Browser, OS, viewport, locale, time zone, and feature flags.

Session timeline

A short clip of clicks and route changes leading up to the report.

Source-map awareness

Stack traces resolve to the original source files when source maps are uploaded.

Custom metadata

Attach plan tier, account ID, or any first-party signal so triage can filter by what matters to you.

Frequently asked questions

How do you handle sensitive form data?
Mark inputs with data-anchormark="redact" and the SDK blurs them in the screenshot and strips them from console payloads. Field-level redaction rules can be defined globally in workspace settings.
What is the SDK overhead?
Under 30 KB gzipped, lazy-loaded, and idle until the reviewer opens the widget. The console buffer uses a fixed-size ring so memory stays flat regardless of how long the page has been open.
Will this slow down my production site?
No measurable impact in our benchmarks. The SDK does no work until a reviewer interacts with it, and the capture buffer is bounded so it never grows unbounded.
Can I attach my own metadata to a report?
Yes — pass an object via AnchorMark.identify() or set per-event metadata at capture time. Everything you attach is searchable and filterable in the AnchorMark dashboard.
Does AnchorMark capture screen recordings?
AnchorMark captures a short timeline of clicks and route changes leading up to a report — not full session replay. Pair with a dedicated replay tool if you need full video; reports can be linked to external recordings via webhook events.
What happens to captured data after a report is resolved?
Captured screenshots, console buffers, and network logs follow the workspace retention policy you configure. Defaults are conservative; Enterprise plans can shorten retention or extend it for audit.

Keep exploring

Pinned visual feedback

Drop pins on any element on a live page or screenshot. Threaded comments stay anchored even when the layout changes.

AI triage

Claude clusters duplicates, drafts severity, and writes the first summary so triage takes minutes, not hours.

Browser extension

Capture pinned feedback on any site you visit — staging, production, or a competitor's page — without an SDK install.

QA review cycles

Run release-readiness review cycles with a shared queue, severity gates, and historical pass/fail by build.

Beta testing

Collect structured beta feedback from real users with the embedded widget and AI-clustered reports.

Ship faster with feedback that already has the receipts.

Start a 14-day trial of the Team plan — no credit card required.

Compare plans