See what your deploy actually changed.
CI tells you the code passed. TrueClara tells you whether the route still works after the deploy — broken URLs, route regressions, and value-route impact, each pinned to the release that caused it.
Built for Next.js teams shipping to production
Your app is a graph. Every deploy changes it.
TrueClara parses your Next.js app into a route graph, then overlays each deploy on top of it — so a release isn’t a list of commits, it’s a picture of which routes and edges actually moved, and which one started costing you.
Three kinds of observation, one SDK.
CI checks the build. Error monitors catch what throws. The regressions that hurt most do neither — they just quietly change behavior on a route users depend on. Those are the ones TrueClara is built to surface.
Broken URLs, found and auto-resolved
Dead links and 404s detected in production, ranked by how many real users hit them. When your next deploy fixes a link, TrueClara marks it resolved on its own — no ticket to chase.
see link health →Route regressions, attributed to the deploy
CUSUM change-point detection watches conversion and reach per route. When one shifts, TrueClara pins it to the exact commit SHA with baseline, current, and confidence — and sends it to Slack.
see deploy attribution →PR impact preview, before you merge
TrueClara posts a Mermaid diagram on the pull request showing which routes the change is predicted to touch — then runs a post-merge retrospective comparing predicted against what actually regressed.
see PR previews →The build passed. The route didn’t.
A deploy can ship clean — tests green, no exceptions, error monitor silent — while a value route quietly stops converting. TrueClara turns that silent shift into a record with evidence: baseline, current, sample size, and statistical confidence.
Same deploy. One of them noticed.
One command. Watching your routes in minutes.
Drop the SDK into any Next.js app on 13.4 or later — App Router or Pages. 15KB gzipped, cookieless, US-only data residency. Parser builds your route graph; the first deploy attaches itself automatically.
npx @trueclara/install
Free while you’re small. Fair as you grow.
Start free on one project, no card. Upgrade when monitoring more projects and longer history earns its keep. Users are tier-limited, never seat-taxed, and there are no usage overages.
See full pricing →The honest FAQ.
What does TrueClara do that CI and my error monitor don’t?
CI tells you the build passed. Error monitors catch what throws — exceptions, 500s, crashes. Neither sees a deploy where nothing errors but a route quietly stops converting, a link silently 404s, or a flow gets abandoned. TrueClara watches the routes users actually travel and attributes any change to the deploy that caused it.
What is the route graph?
TrueClara’s parser turns your Next.js app into a deterministic graph of routes and the edges between them. Runtime telemetry matches against it, and every deploy is overlaid as a diff — so you see which routes and edges a release changed, not just a list of commits.
What does CUSUM actually do?
CUSUM is a change-point detection method. Instead of alerting on a single bad data point, it accumulates small deviations and fires when a metric has genuinely shifted — which is why it catches a sustained 18% drop that a threshold would miss, with a sample size and confidence attached.
Does the SDK need access to my codebase or database?
No. The SDK reports out from the browser and edge — it has no read access to your source, your production database, or your deploy infrastructure. You install it, it observes route behavior, it reports findings. PR previews clone in an isolated worker, not from your running app.
Is it GDPR-safe?
Cookieless aggregate mode by default, no fingerprinting, US-only data residency. Session-level behavior is opt-in via an explicit analytics consent mode. There’s nothing to put in a cookie banner unless you turn that on.
What’s coming next?
Native Vercel Marketplace install, route-anchored Core Web Vitals (INP/LCP/CLS) regression detection, and auth-flow regression tracking — all attributed to the deploy, all on the same route graph.
Ship fast. Know the same minute what changed.
Install the SDK, link your repo, connect Slack — and never again learn about a silent route regression from a customer email.