Your backend,
in plain sight.

Find the slow routes. Understand the errors.
Give your customers a clear view of service health.

Start monitoring Open workspace Explore the platform

Small Express SDKZero runtime dependenciesNo request bodies collected

your workspace / tracenestIllustrative data

ACME API / PRODUCTION

Your application, at a glance.

Last hour

Total requests24,812

Requests in this window

Server error rate0.6%

5xx responses, separated from 4xx

p95 latency84.3ms

Approximate 95th percentile

p99 latency186.7ms

See beyond the average

Request volumeRequests

6004002000

Response breakdown

99.4%Non-5xx responses

2xx4xx5xx

Example data. Your workspace displays your own traffic.Try the tabs above

BUILT FOR YOUR BACKEND. AT HOME IN YOUR STACK.

Node.js 22+ExpressTypeScriptMongoDBYour infrastructure

ONE CONNECTED WORKSPACE

Less digging.
More understanding.

From an individual request to the health of your service.
The context you need, without a heavy SDK.

REQUEST EXPLORER

The response tells the story.

Inspect the method, route, exact HTTP status, and duration. Filter by endpoint, status, or minimum response time.

Useful paths · Exact status codes

PERFORMANCE ANALYSIS

Go beyond the average.

Compare p50, p95, and p99 latency. Find slow requests and see how an individual response compares with its endpoint.

Percentiles · Endpoint comparisons

PUBLIC STATUS PAGES

Keep your customers in the loop.

Enable a public service-health page and copy its URL or website link. Share aggregate health while request details stay private.

Shareable URL · 24-hour history

HEALTH MONITORING

Check health. Keep the load light.

Scheduled health checks work even when your app has no traffic. Timeouts, concurrency limits, and stored results keep checks bounded.

60-second interval · 3-second timeout

PRIVACY & DELIVERY

Collect the signal you need.

Request bodies, query strings, and headers are excluded. Redact sensitive path segments and inspect SDK delivery statistics.

Metadata only · Bounded exports

PROJECT CONTROL

A home for every environment.

Separate production from staging, rotate environment write keys, and choose how long new telemetry is retained.

Scoped keys · Retention controls

FREE · PRO · ENTERPRISE

A clearer backend.
At every stage.

Start exploring with Free. Pro and Enterprise are previews.
Paid pricing and plan limits have not been announced.

Free

Find your first signal. Get to know your backend.

Free

A starting point for your Express application.

Start monitoring Open workspace

Explore your application

Request methods, routes, and status codes
Response duration and request filters
Small SDK with bounded background exports

Node.js 22+ · Express

FOR YOUR NEXT CHAPTER

Pro

A bigger picture of performance and service health.

Coming soon

Paid pricing and plan limits are being finalized.

Explore a budget

Understand production traffic

p50, p95, and p99 latency analysis
Endpoint comparisons and slow requests
Public status pages and health monitoring

Preview · final inclusions to be confirmed

Enterprise

Bring your services and environments into focus.

Coming soon

Paid pricing and plan limits are being finalized.

Read deployment guidance

Organize your environments

Separate production and staging environments
Scoped write keys and key rotation
Configurable retention for new telemetry

Preview · final inclusions to be confirmed

The feature groupings above illustrate each plan’s focus. Final paid entitlements and limits are not yet published. There is no paid checkout or purchase on this page.

Keep the integration small.

Start with the same lightweight Express SDK. Your request metadata, analysis, and service health stay connected.

Integration guide

A HYPOTHETICAL BUDGET

Plan around your traffic.

Choose your request volume and an assumed rate. This is a planning tool, not a TraceNest price quote.

Add your rateEnter an assumed rate to calculate a budgetAssumed USD per 1 million requestsNo TraceNest rate or yearly discount is assumed.

Monthly request volume1M

1,000,000 requests / month

Connect your application

SERVICE HEALTH, OUT IN THE OPEN

A little reassurance.
A link away.

Give your customers a status page they can actually use. Add the generated link to your website and let scheduled health checks keep it informed.

Public by choice. Enable a page for one project environment. Disable it when you need to.
Checks that stay lightweight. At most one per minute, with a three-second timeout and no immediate retries.
Honest about what it knows. Consecutive failures show disruption. Stale checks show unknown status.

Create your status page Open workspace

PUBLIC STATUS PAGEExample

Acme APIService status

All systems operationalHealth endpoint responded successfully

Health-check historyPast 24 hours

24 hours agoNow

HTTP 20028 ms response60 s interval

tracenest.example/status/your-page

More page views. Same check frequency.Public visitors read stored results. They never trigger additional requests to your backend.

60 secMinimum check interval

3 secTotal timeout per check

2 checksConcurrent per API process

Private detailsOnly aggregate health is public

SMALL SDK. BIGGER PICTURE.

A few lines.
A lot more clarity.

Keep the integration small. Let TraceNest handle the analysis and health monitoring in the backend.

01
Create a project
Choose an environment and save its generated write key.
02
Connect your Express app
Build and install the SDK. Add middleware before your routes.
03
Send a request. Follow the signal.
Open your dashboard, inspect traffic, and enable a public status page.

Read the integration guide

app.cjs

1const { createTraceNest } = require('tracenest-node');
2
3const telemetry = createTraceNest({
4  endpoint: process.env.TRACENEST_ENDPOINT,
5  projectId: process.env.TRACENEST_PROJECT_ID,
6  environment: process.env.TRACENEST_ENVIRONMENT,
7  apiKey: process.env.TRACENEST_WRITE_KEY,
8  onError: (error) => console.error('[TraceNest]', error),
9});
10
11app.use(telemetry.middleware); // Before your routes
12app.get('/products/:id', handler);

Visibility with clear boundaries.

No request bodies, query strings, cookies, or authorization headers. Paths can contain IDs; use route redaction for sensitive segments. Public status pages share aggregate health, while individual requests stay in your private workspace.

Read the docs

DEVELOPER PERSPECTIVES

Less friction. More clarity.

Sample testimonials — illustrative copy, not customer endorsements.

I want to see the route, the exact status code, and how long the response took—all in one place.

Example backend engineerRequest analysis · Sample

An average is a starting point. Seeing p95 and p99 helps me understand the requests that need attention.

Example tech leadPerformance insights · Sample

A simple status link gives my customers a place to check service health without sharing private request details.

Example indie founderPublic status pages · Sample

I want to see the route, the exact status code, and how long the response took—all in one place.

Example backend engineerRequest analysis · Sample

An average is a starting point. Seeing p95 and p99 helps me understand the requests that need attention.

Example tech leadPerformance insights · Sample

A simple status link gives my customers a place to check service health without sharing private request details.

Example indie founderPublic status pages · Sample

Health checks should stay predictable. A bounded check interval and a short timeout make the load easier to reason about.

Example platform engineerHealth monitoring · Sample

I want a small integration: add the middleware, send a request, and follow the signal in my dashboard.

Example Node.js developerExpress integration · Sample

Keeping production and staging separate makes it easier to understand which environment needs our attention.

Example engineering managerProject controls · Sample