See what matters.

WizeLens shows you everything one request did. The click in React, your .NET and Node services, every SQL query, and the render, on one timeline. The problems are found for you.

Get started View on GitHub

Open source under MIT. For .NET 10, Node, React, and Next.js.

GET /api/customers-with-orders

8:54:51 PM · 305 ms · gateway-api

Timeline

fetch /api/customers-with-orders270 ms

GET /api/customers-with-orders263 ms

gateway-api · 9 queries7.9 ms

GET localhost:5291/orders45 ms

GET /orders3.9 ms

SELECT orders0.3 ms

Insights · 2

N+1 queryN+1 query: ran 8 times2.9 ms

SELECT "c"."Id", "c"."Email", "c"."Name" FROM "Customers"…

N+1 HTTPN+1 HTTP: GET /orders ran 8 times45 ms

GET localhost:5291/orders?customerId=…

WizeLensGET /api/customers-with-orders200

305 msTotal

263 msServer

9.6 msDatabase

35 msRender

17 SQL8 Fetch2 Insights

One click. Every hop.

01
You click.
A button in your React app calls the API. WizeLens adds a traceparent header, so the server knows which click sent it.
02
The gateway answers.
Your .NET gateway runs the handler and its EF Core queries. Routing, handler, and every statement are timed.
03
It calls the next service.
The Node orders API gets the same trace id. Its response says where its own WizeLens lives, so nothing is set up by hand.
04
Every query is caught.
Both databases: each statement, its time, and its parameters. Passwords, tokens, and keys are redacted before anything is stored.
05
One timeline.
Open the trace in any service. It pulls the pieces from the others and shows one request, end to end. There is no collector to run.

GET /api/customers-with-orders · 305 ms · 36 spans · 3 services · 2 insights

Eight queries. One would do.

You did not ask WizeLens to look for this. It looks at every trace for the mistakes that slow real apps down, ranks them, and tells you how to fix them.

N+1 queries
N+1 HTTP calls
Duplicate queries
Slow queries
Errors
Render hot spots

The same rules run in .NET and in Node, so every service gives the same answer.

orders-api · GET /orders

Everything a request touched.

Ten dashboard pages, one look. Requests, traces, database, rendering, errors, logs, metrics, services, and insights, for one service or all of them.

Every query, from any ORM.

EF Core, Dapper, Prisma, Drizzle, TypeORM, or the raw driver. Each statement with its time and where it came from.

SELECT "c"."Id", "c"."Name" FROM "Customers"2.1 ms

EF Core

SELECT id, total FROM orders WHERE customer_id = ?0.4 ms

node:sqlite

SELECT * FROM order_lines ORDER BY created_at398 ms

Dapperslow

INSERT INTO orders (customer_id, total) VALUES …6.1 ms

Prisma

UPDATE stock SET qty = qty - $1 WHERE sku = $23.4 ms

Drizzle

SELECT name FROM products WHERE id = ANY($1)1.2 ms

EF CoreDapperADO.NETPrismaDrizzleTypeORMpgmysql2better-sqlite3node:sqlite

Renders, timed per component.

React renders, hydration, and Web Vitals for each page.

<ProductCard />× 031 ms

<CartBadge />× 02.4 ms

<PriceTag />× 01.1 ms

LCP 1.2 sINP 88 msCLS 0.02

Errors, with the request around them.

The stack, the request, and the spans that led to it. Browser errors too.

InvalidOperationExceptionGET /api/boom · 500

Sequence contains no elements

at System.Linq.Enumerable.First[T](IEnumerable`1 source)at Gateway.BoomController.Get() in BoomController.cs:line 42at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor

Logs from every logger.

Serilog, NLog, ILogger, pino, winston, bunyan, console, and more, linked to their trace.

infogateway-apiSerilogLoaded 8 customers

infoorders-apipinoGET /orders 200 in 3.9 ms

warnorders-apipinoQuery took 398 ms on order_lines

infowebconsoleCart updated (3 items)

errorgateway-apiILoggerSequence contains no elements

infobillingwinstonInvoice 1042 sent

debuggateway-apiNLogCache hit: products:all

infosearchbunyanIndex refreshed (24 docs)

warnwebconsoleImage hero.jpg took 1.4 s

infogateway-apiSerilogLoaded 8 customers

infoorders-apipinoGET /orders 200 in 3.9 ms

warnorders-apipinoQuery took 398 ms on order_lines

infowebconsoleCart updated (3 items)

errorgateway-apiILoggerSequence contains no elements

infobillingwinstonInvoice 1042 sent

debuggateway-apiNLogCache hit: products:all

infosearchbunyanIndex refreshed (24 docs)

warnwebconsoleImage hero.jpg took 1.4 s

Metrics next to the traces.

CPU, memory, GC, and your own OpenTelemetry counters, per service.

CPU23%

Memory184 MB

GC / min4

Who calls whom.

Every service, database, and outside host, on one map.

Ctrl K finds it.

Search requests, traces, errors, and services.

Ctrl K

Keep a share. Keep every error.

Sampling picks the same traces in every service. A trace with an error or a slow span is always kept.

20% sampleerrorsslow21 of 72 kept

Secrets never get stored.

Passwords, tokens, cookies, and connection strings are redacted before anything is written.

content-typeapplication/json

authorizationBearer eyJhbGciOiJIUzI1NiJ9.e30

cookiesession=4f9c2a7d1b

x-request-id7c1e-42aa

connectionStringHost=db;Password=hunter2

Your AI can look. Only if you let it.

There is no AI inside WizeLens. There is a door: a read-only MCP endpoint that your own agent can use to read traces, slow queries, N+1 problems, and errors. You decide if it opens.

Off by default. Nothing is reachable until you turn it on, per service.
Read-only. No tool can change anything. It can only look.
Redacted. Secrets are replaced before they are stored, so an agent never sees them.
Audited. Every call writes a line to your log. In the cloud, Claude signs in and reads only the projects you pick.

builder.Services.AddWizeLens(o => o.EnableMcp = false);

get_overviewget_timeseriesgroup_requestslist_tracesget_tracefind_slow_queriesfind_n_plus_oneget_errorssearchget_metric

Open /_wizelens. That's it.

Every service serves the dashboard on its own port. No account, no agent, no collector. Your data stays on your machine until you send it somewhere.

localhost:5100/_wizelens/overview

WizeLens Overview page: Requests, timing, services, and insights at a glance.

Two lines in .NET. One in Node.

Add the package, add a line, run your app. WizeLens is on in development and off in production unless you turn it on.

Two lines. Add WizeLens.EntityFrameworkCore and one call for EF Core queries.

Program.cs

1using WizeLens;
2
3builder.Services.AddWizeLens();
4builder.Services.AddDbContext<AppDb>(o =>
5    o.UseSqlServer(cs).UseWizeLens());
6
7var app = builder.Build();
8app.UseWizeLens();

Start in one app. Grow to a team.

The same dashboard at every step. Move up when you need to, and not before.

In your app

MIT

One package per service. Each keeps its traces in a small SQLite file, so they survive a restart.

Dashboard at /_wizelens
Newest 2,000 traces or 24 hours
Traces across services, with no collector

The local hub

MIT

Every service sends to one place on your machine or your network, also when a service is stopped.

7 days in one SQLite file
Projects and environments
Any language over OpenTelemetry

npx @wizeworks/lens-hub

WizeLens Cloud

Self-hosted

The same dashboard for a whole team, with history, alerts, and links you can share.

Organizations, roles, and invites
7- and 30-day history
Alerts to webhooks and Slack

Works with what you already run.

.NET 10, Node 22, and React 18 or newer. Anything else that speaks OpenTelemetry can send to the hub.

Frameworks

ASP.NET Core
Express
Fastify
Koa
Hono
Next.js
node:http
React

Databases and ORMs

EF Core
Dapper
ADO.NET
Npgsql
SqlClient
MySqlConnector
Prisma
Drizzle
TypeORM
pg
mysql2
better-sqlite3
node:sqlite

Messaging and RPC

gRPC
RabbitMQ
Kafka
Azure Service Bus
MassTransit
HttpClient
fetch

Logging

ILogger
Serilog
NLog
console
pino
winston
bunyan
log4js
consola
NestJS

Open standards

OpenTelemetry
OTLP
W3C traceparent
MCP

Questions, answered.

The short version of what people ask first. The docs have the long version.

What is WizeLens?

WizeLens shows you everything one request did. You add a small package to your .NET, Node, or React app, and every request becomes one trace: the click in the browser, every service it touched, every SQL query, every log line, and the render. A dashboard at /_wizelens shows it, and a small HUD in the corner of your page shows the latest request as you work.

Is WizeLens free?

Yes. The add-ons, the local hub, and the cloud service are open source under the MIT License. You can use them in any project, including paid ones, and run them yourself for free. The hosted WizeLens Cloud has a Free plan and paid plans for more data and history.

Is WizeLens a replacement for Glimpse?

In spirit, yes. Glimpse showed what one ASP.NET request did. WizeLens does that for ASP.NET Core on .NET 10, for Node, and for React and Next.js, and it follows the request through every service, built on OpenTelemetry. WizeLens is an independent project and is not affiliated with Glimpse.

How is WizeLens different from an APM or observability platform?

Observability platforms watch production fleets. WizeLens is made for the developer at the desk: two lines of setup, no account, no agent, and no collector. It points at the problem, such as an N+1 query, instead of only showing data. When a team needs history and alerts, the same dashboard runs in the local hub or WizeLens Cloud.

Does WizeLens send my data anywhere?

No. Traces stay in your app, your own hub, or your own cloud database. The software sends no telemetry to WizeWorks. Passwords, tokens, cookies, and keys are redacted before anything is stored.

Can I run WizeLens in production?

WizeLens is on in development and off in production unless you turn it on. If you do, it is send-only: it sends traces to your cloud or hub, and the app serves no dashboard or read API. Sampling keeps a share of the traces plus every trace with an error or a slow span. WizeLens is in alpha today.

Does WizeLens use AI?

There is no AI inside WizeLens. It has an optional, read-only MCP endpoint that your own AI agent, such as Claude, can use to read traces, slow queries, N+1 problems, errors, and a health report. In the cloud, Claude signs in and reads only the projects you pick. It is off by default, redacted, and every call is logged.

What does WizeLens work with?

ASP.NET Core on .NET 10, Node 22.13 or newer (Express, Fastify, Koa, Hono, Next.js), and React 18 or newer. Databases through EF Core, Dapper, ADO.NET, Prisma, Drizzle, TypeORM, pg, mysql2, and SQLite. gRPC, RabbitMQ, Kafka, and Azure Service Bus. Any other language can send OpenTelemetry to the hub.

Inspect. Understand. Build better.

Better software starts with better visibility.

Get started Star on GitHub

See what matters.

Timeline

Insights · 2

One click. Every hop.

You click.

The gateway answers.

It calls the next service.

Every query is caught.

One timeline.

Eight queries. One would do.

Everything a request touched.

Every query, from any ORM.

Renders, timed per component.

Errors, with the request around them.

Logs from every logger.

Metrics next to the traces.

Who calls whom.

Ctrl K finds it.

Keep a share. Keep every error.

Secrets never get stored.

Your AI can look. Only if you let it.

Open /_wizelens. That's it.

Two lines in .NET. One in Node.

Start in one app. Grow to a team.

In your app

The local hub

WizeLens Cloud

Works with what you already run.

Frameworks

Databases and ORMs

Messaging and RPC

Logging

Open standards

Questions, answered.

What is WizeLens?

Is WizeLens free?

Is WizeLens a replacement for Glimpse?

How is WizeLens different from an APM or observability platform?

Does WizeLens send my data anywhere?

Can I run WizeLens in production?

Does WizeLens use AI?

What does WizeLens work with?

Inspect. Understand. Build better.

One click. Every hop.

You click.

The gateway answers.

It calls the next service.

Every query is caught.

One timeline.

Eight queries. One would do.

Everything a request touched.

Every query, from any ORM.

Renders, timed per component.

Errors, with the request around them.

Logs from every logger.

Metrics next to the traces.

Who calls whom.

Ctrl K finds it.

Keep a share. Keep every error.

Secrets never get stored.

Your AI can look. Only if you let it.

Open /_wizelens. That's it.

Two lines in .NET. One in Node.

Start in one app. Grow to a team.

In your app

The local hub

WizeLens Cloud

Works with what you already run.

Frameworks

Databases and ORMs

Messaging and RPC

Logging

Open standards

Questions, answered.

What is WizeLens?

Is WizeLens free?

Is WizeLens a replacement for Glimpse?

How is WizeLens different from an APM or observability platform?

Does WizeLens send my data anywhere?

Can I run WizeLens in production?