request-first tracing for backend developers

See every request,
before it becomes an incident.

TraceFlow is a request-first API and tracing tool for backend developers — capture a request, inspect its trace, and get more context without leaving the same workflow.

clientgateway4msauth-svc8msorders-svc22msbilling-svc41msinventory-svc17mspostgres63ms
Built around the problems backend developers actually face
EXPRESSNODE.JSBACKENDREQUESTSTRACESAPIDEBUGGINGOBSERVABILITYTRACEFLOWDEVELOPEREXPRESSNODE.JSBACKENDREQUESTSTRACESAPIDEBUGGINGOBSERVABILITYTRACEFLOWDEVELOPER
capabilities

A focused workflow around requests and traces

The core surfaces stay close to the request, so you can inspect what happened without unnecessary context switching.

Request tracing

Capture API requests as traces and inspect the information attached to each request.

Request details

See method, route, status, duration, and other request information in one place.

Trace history

Review captured traces for a project and find slow or failed requests faster.

Project trace explorer

Keep traces organized by project so you can move from an application to the requests it has captured.

Response context

See status codes and request timing together, giving failed or slow calls more context.

API workflow

Hit an API, inspect its response, and use the same workflow to understand what happened to the request.

the request lifecycle

One request, from call to context

Make the request. Capture the trace. Inspect what happened.

  1. API Requestsend the request
    01
  2. Trace Capturerecord request context
    02
  3. Trace Detailsinspect method + route + status + duration
    03
  4. Project Dashboardreview captured requests
    04
request workflow

Send the request. Keep the context.

TraceFlow starts with the request itself. Make an API call, capture its trace, and inspect useful request information without losing the context of what you just sent.

  • Request and trace in one workflow
  • Method, route, status, and duration at a glance
  • Project-level trace history
orders.service.ts
▍
product

A dashboard built around the request

The interface keeps request context visible while you inspect the trace.

Request activitysample
Request timingsample
Trace timeline — examplesample
gateway
auth-svc
orders-svc
billing-svc
postgres
trace-store
Request path — example
Response status
2.1%
example response
Request duration
124ms
example timing
API
Request-first workflow
TRACE
Captured request context
1
Place to inspect request + trace
SOON
Pricing
the idea behind TraceFlow

Built around a simple debugging idea

“A request should not disappear the moment you hit send. It should leave enough context to understand what happened.”

T
TraceFlow principle
Request-first debugging

“The goal is simple: give developers more information about the request without making them jump between tools just to investigate it.”

T
TraceFlow goal
Developer workflow

“When something is slow, the useful question is not only whether it is slow. It is where the time is actually going.”

T
TraceFlow direction
Bottleneck discovery
pricing

Pricing is coming soon

TraceFlow is still being actively built. We want to understand the product, usage patterns, and infrastructure costs before introducing pricing.

Built first. Priced thoughtfully.

The current focus is on building a useful tracing experience for Express developers, solo developers, and startups. Pricing will be announced once the product is ready for its next stage.

COMING SOON
faq

Good to know

TraceFlow is an API and tracing tool focused on helping backend developers capture requests, inspect their traces, and understand what happened during a request.

The current focus is Express and backend developers, including solo developers and startups that want a straightforward way to inspect their API requests and traces.

Instead of only seeing an API response, TraceFlow gives the developer more information about the request so they can track it and investigate where a problem or bottleneck is occurring.

TraceFlow was inspired by working with existing tracing tools such as Jaeger. The goal is to provide a request-focused environment where developers can inspect the trace without losing the context of the request itself.