Observability for the errors that slip through.

Server errors are reachable, but frontend failures go untracked. Capture exceptions that escape your testing pipeline but surface for real users.

docker run --rm -p 48043:8080 vantmetry/demo

Spin up a local, private demo. No sign-ups required.

Core Capabilities

Automated Exception Capture

WebTransport and HTTP/3 powered near-instant telemetry for production visibility without head-of-line blocking. Falls back to sendBeacon on unsupported browsers. Learn how the ingestor processes events at scale.

Privacy-First Telemetry

Client-side redaction of emails and auth tokens before data ever leaves the browser. See our privacy notice for details.

Real-time Monitoring

Built-in monitoring and spike detection thresholds with webhook-based alerting.

Ready to dive in?

Explore our guides on tracker integration, automatic source map resolution, and analytical querying.

Read Documentation

Start catching errors today

No infrastructure to manage. Predictable pricing with automatic log rotation that keeps storage costs from creeping up.

Start your trial

or ask agent to do it

Add Vantmetry error tracking to this project. Install the CLI:
npm install -g vantmetry-cli
Then check docs: https://vantmetry.com/docs or run:
vant help or vant register or vant trial

Frequently Asked Questions

What is frontend observability?

Frontend observability is the ability to understand and monitor what happens in the browser. It captures JavaScript errors, exceptions, and performance metrics that traditional backend monitoring cannot see. Vantmetry lets you see every error that real users encounter.

How is Vantmetry different from Sentry or LogRocket?

Vantmetry is a lightweight, focused error tracker built for frontend observability. Sentry is a broader observability platform covering backend, mobile, and performance monitoring. LogRocket adds session replay and heatmaps on top of error tracking. Vantmetry keeps things simple with predictable pricing based on log volume and automatic log rotation.

How does the tracker avoid blocking the main thread?

The Vantmetry tracker uses WebTransport (QUIC/HTTP3) for unidirectional event streams that do not block JavaScript execution. On browsers without WebTransport support, it falls back to sendBeacon and fetch with keepalive, both of which are non-blocking network primitives. Learn more in the tracker documentation.

What PII does Vantmetry mask, and how?

Client-side redaction masks email addresses, phone numbers, and common auth token patterns before data ever leaves the browser. PII detection runs on every error message and stack trace, so you capture the error without exposing sensitive user data.

How much does Vantmetry cost?

Vantmetry uses predictable pricing based on log volume. You pay for the events you store, not per error or per user. Automatic log rotation keeps storage costs predictable, and there are no surprise overage charges.