# Nevision

> All-in-one observability for web apps and servers: session replay, JavaScript error tracking, uptime monitoring, Core Web Vitals, frontend & backend logs, plus server CPU and memory metrics. One lightweight script. Free plan, no credit card.

Nevision combines tools that are usually separate (Sentry for errors, LogRocket for replay, Pingdom for uptime, Datadog for server metrics) into a single product with a single script tag. Privacy-first: passwords and emails are masked automatically.

## Product

- [Pricing](https://nevision.app/pricing): Free, Lite ($12/mo), Pro ($39/mo), Business ($99/mo). All paid plans include every feature.

## Features

- [Session Replay](https://nevision.app/session-replay): Pixel-perfect 60fps user session recordings with full DOM reconstruction.
- [Error Tracking](https://nevision.app/error-tracking): JavaScript runtime error capture with automatic grouping by fingerprint and stack traces.
- [Uptime Monitoring](https://nevision.app/uptime-monitoring): HTTP checks at 1/5/15-minute intervals with email alerts on downtime and recovery.
- [Performance Monitoring](https://nevision.app/performance-monitoring): Core Web Vitals (LCP, INP, CLS, TTFB, FCP) with per-page breakdowns.
- [Server Monitoring](https://nevision.app/server-monitoring): Real-time CPU, memory, disk, and network metrics from your servers.
- [Log Management](https://nevision.app/log-management): Structured frontend and backend logs linked to sessions.
- [Web Analytics](https://nevision.app/web-analytics): Privacy-friendly, cookieless page view and visitor analytics with referrer, country, and device breakdowns.

## Documentation

- [Quickstart](https://nevision.app/docs/quickstart): Install the Nevision recorder and watch your first session in 60 seconds.
- [Install via script tag](https://nevision.app/docs/install-script-tag): The simplest install method — works with any HTML page.
- [Privacy masking](https://nevision.app/docs/privacy-masking): How session recordings handle PII and how to mask custom fields.
- [Configuring uptime monitors](https://nevision.app/docs/uptime-monitors): Add HTTP checks for your sites and APIs.
- [Report errors from your backend](https://nevision.app/docs/backend-error-reporting): Send errors from Python, PHP, .NET, Java, Kotlin, and iOS Swift via a single POST.
- [Send frontend logs](https://nevision.app/docs/frontend-logs): Stream browser-side logs (warnings, captured errors, custom events) into Nevision via a single POST. JavaScript and TypeScript examples.
- [Send backend logs](https://nevision.app/docs/backend-logs): POST structured backend log events from Node.js, Python, PHP, Go, Ruby, .NET — language-agnostic with curl.
- [Send server metrics (CPU, memory, disk)](https://nevision.app/docs/server-metrics): Push CPU, memory, disk, and network metrics from any host. Bash, Python, Node.js, Go, and curl examples.

## Blog

- [How to debug INP regressions in production](https://nevision.app/blog/debug-inp-regressions): INP replaced FID as the Core Web Vital for interactivity. Here's how to find which interactions on which pages are slow — and what to do about it.
- [Session replay vs. error tracking: when to use each](https://nevision.app/blog/session-replay-vs-error-tracking): They're often bought together but solve different problems. Here's when each one is the right tool — and why most teams need both.
- [GDPR-compliant session recording: what to mask and why](https://nevision.app/blog/gdpr-session-recording): Session recording is legal under GDPR if you do it right. Here's the practical playbook for masking PII, configuring retention, and handling DSARs.
- [Uptime monitoring best practices for 2026](https://nevision.app/blog/uptime-monitoring-best-practices): Going beyond basic ping checks: multi-region probes, expected response validation, and how to avoid the noisy-alert death spiral.
- [How to correlate frontend and backend logs (for real)](https://nevision.app/blog/frontend-backend-log-correlation): Stitching together a user complaint with the backend log line that explains it shouldn't take 30 minutes of grep. Here's the pattern that actually works.

## Comparisons

- [Nevision vs Sentry](https://nevision.app/alternatives/sentry): Best Sentry alternative when you also need session replay, uptime, and server metrics
- [Nevision vs LogRocket](https://nevision.app/alternatives/logrocket): Best LogRocket alternative — same pixel-perfect replay, but with errors, uptime, and server metrics included
- [Nevision vs Hotjar](https://nevision.app/alternatives/hotjar): Best Hotjar alternative for product teams who need debugging, not just heatmaps
- [Nevision vs UptimeRobot](https://nevision.app/alternatives/uptimerobot): Best UptimeRobot alternative when you also need replay, errors, and server metrics
- [Nevision vs Datadog](https://nevision.app/alternatives/datadog): Affordable Datadog alternative for teams that don't need enterprise APM complexity
- [Nevision vs FullStory](https://nevision.app/alternatives/fullstory): Affordable FullStory alternative for teams without enterprise sales cycles

## Integrations

- [React](https://nevision.app/integrations/react): Drop the recorder script into your index.html — no npm package, no bundler config.
- [Next.js](https://nevision.app/integrations/nextjs): A single next/script tag in your root layout (works for App Router and Pages Router) is all you need.
- [Vue](https://nevision.app/integrations/vue): Vue 2 and Vue 3 are both supported.

## Optional

- [Changelog](https://nevision.app/changelog)
- [Privacy Policy](https://nevision.app/privacy)
- [Terms of Service](https://nevision.app/terms)