Features

Every layer.Its own instrument.

Eight deeply integrated surfaces, one workspace. Here is what Inspectro sees when it looks inside your frontend.

01 — Debug

Debug the server your browser never could.

The one thing no other frontend tool does: step through server-rendered and Node/API code over CDP, with breakpoints synced bidirectionally to VS Code — SSR stops being a blind spot. Client-side debugging is in beta.

inspectro — debugBREAKPOINT HIT
Inspectro Debug panel
02 — Inspector

See your component tree. Jump straight to source.

Select any element in the preview and Inspectro reveals its component, props, state and the exact line of source that rendered it. Edit React props live and watch the UI update instantly.

Write-back to source
inspectro — inspectorLIVE
Inspectro Inspector panel
03 — Network

Record continuously. Pause when it matters.

Every request, response, header and payload — captured as it happens, correlated with the component that triggered it. The failing checkout call is never a mystery again.

inspectro — networkRECORDING
Inspectro Network panel
04 — Performance

Measurement, not generic analytics.

Render counts, average render time and the triggering context for every component in the tree. Find the ResultsList re-rendering 27 times before your users feel it.

inspectro — performanceRECORDING
Inspectro Performance panel
05 — Cookies & Environments

Own your cookies. Environments next.

Create, edit and delete cookies for the running app right in the panel — the session state you control, without a browser round-trip. Start each project with a clean jar when you need isolation.

Env & user switching
inspectro — cookiesDEV
Inspectro Cookies panel
06 — Accessibility

A11y as an engineering workflow, not a checkbox.

Severity-filtered audits wired to the exact component at fault. Errors, warnings and passes stream in as you fix them — accessibility becomes part of the build, not a launch-week panic.

inspectro — accessibility3 ERRORS
Inspectro Accessibility panel
07 — Code Coverage

Coverage that lives next to your source.

Load .lcov from your latest run and see line, branch and function coverage per file — mapped to the branch you're on, exportable as JSON for CI.

inspectro — coverageLCOV LOADED
Inspectro Coverage panel
08 — Preview

Click-to-source, straight from the running UI.

A live preview with device toolbar, debug paint overlays and full ancestry. Hover a component, see its hierarchy, open it in the browser — or in your editor.

inspectro — previewCONNECTED
Inspectro Preview panel
UI Time Machine
On the roadmap

Don't just inspect where your UI is.Understand how it got there.

Timeline replay — scrub any component back through every render, prop and network event that shaped it. A preview of where Inspectro is headed.

00:00.000

01Initial render

ProductCard mounts with price 249.00 and zero interaction state.

00:01.204

02State change

User opens the size selector — local state flips, one re-render.

00:02.871

03Prop change

Parent passes a discount prop. Diff captured and highlighted.

00:03.412

04Network response

Inventory call resolves and injects stock count into props.

00:03.498

05Re-render

PriceTag re-renders with the resolved campaign price.

00:04.102

06Current state

Scrub back to any snapshot. The UI rewinds with it.

How Inspectro Works

Not a UI wrapper.
A signal pipeline.

A lightweight runtime lives inside your app and streams instrumentation to the DevTool in your editor — bidirectionally.

Your Application
Any modern frontend
Inspectro Runtime
In-page signal layer
Instrumentation
Components · network · render
VS Code DevTool
The workspace surface
You
Total understanding
Field Guide

"I scout the runtime so you don't have to."

UNIT: INSP-01STATUS: OBSERVING
The Inspectro Manifesto
01

Every bug is observable.

It lives in a layer — a render, a request, a server path. See the layer and you've found the bug. We build instruments, not opinions.

The list re-rendering 27× — visible in Performance.
02

What you can see, you can fix.

The hard ones hide where the browser won't look: SSR execution, the prop that arrives undefined, the call that fired three components deep. We put them on screen.

The SSR path that only throws on the server — steppable in Debug.
03

We make the invisible obvious.

Component, source and runtime, connected live — one continuous surface of truth, no blind spots between tools. See the invisible.

component ↔ source ↔ runtime, connected live.

Ready to look inside your frontend?

Get Early Access