_{Built on OpenTelemetry}

Website · Docs · Cloud · Discord

Traceway is an OpenTelemetry-native observability platform that combines logs, traces, metrics, session replay/RUM, exceptions, and AI tracing together. Point an OTLP exporter at it and you're in business. No Collector, no glue code, no per-language vendor SDK.

MIT licensed. No BSL. No "open core." Every feature is in the box. Self-host it for free, or run it on Traceway Cloud if you'd rather not babysit infra.

👋 Join the Traceway Community on Discord →
_{Chat with the team, shape the roadmap, get help, and meet other folks running Traceway in production.}

• Logs — Structured, trace-linked, sub-second search. Native OTLP/HTTP ingest from any OTel SDK.
• Traces — End-to-end span waterfalls across every service. Click a log, jump to its span.
• Metrics — Host, runtime, and custom metrics. Any dimension, any chart, with custom widget groups.
• Exceptions — SHA-256 normalized stack traces grouped into ranked issues. Source-mapped (webpack, esbuild, Vite).
• Session Replay — Watch what the user did right before the error. Available for web (any JS framework) and Flutter.
• AI Observability — LLM cost, tokens, latency, and full conversations across providers (OpenRouter and any OTel-compatible AI gateway).

Plus: configurable alerts (Slack / GitHub / email / webhook / Pushover / Telegram), Apdex + Impact-Score endpoint ranking, multi-tenant orgs with role-based access, and a per-endpoint slow-threshold override.

Your agent sets up Traceway, queries production telemetry, and finds the root cause:

npx skills add tracewayapp/traceway

One command installs two skills into Claude Code, Cursor, Codex, or any agent that reads SKILL.md:

• /traceway-setup reads your repo and wires it up: OTel for backends, Traceway SDKs for web and mobile. Then it verifies data actually arrives.
• /traceway installs the traceway CLI and uses it to query exceptions, logs, endpoints, and metrics, from bug report to root cause.

The CLI is designed for agents first: JSON when piped, tables on a TTY, stable error identifiers and exit codes, --fields to trim responses. It is read-only apart from archiving exceptions, which requires an explicit --yes, so nothing hangs and nothing gets damaged.

The skills are plain Markdown in skills/, in the same MIT-licensed repo. No marketplace, no lock-in. Learn more →

app.min.js:1:63 tells you nothing. Traceway resolves minified production errors back to the original file, line, and function the moment they arrive.

The symbolicator is pure Go and built to keep up with ingest. Each source map compiles once into a binary .tw file and is memory-mapped from disk: under a microsecond to open a compiled map, p99 lookup under a millisecond on a cold cache, zero maps re-parsed after a restart. The corpus is a disk budget, not a RAM budget.

The same engine ships as a standalone OpenTelemetry Collector processor, drop-in compatible with Honeycomb's source_map_symbolicator: same component type, same attribute contract, same config keys. Use it in your own pipeline, with or without Traceway behind it.

Upload maps from CI with npx traceway-sourcemaps --directory ./dist. Benchmarks live in benchmarks/; run them on your fork. Learn more →

git clone https://github.com/tracewayapp/traceway
cd traceway && docker compose up -d
# ✓ dashboard at http://localhost

Point any OTel SDK at http://localhost/api/otel/v1/traces (or /metrics, /logs) and traces start flowing. See the self-hosting docs for production deployment, TLS, and storage configuration.

Docker images are cryptographically signed. See DOCKER_SIGNATURES.md to verify images before deploying.

Run Traceway inside your Go process — no Docker, no external databases, SQLite under the hood:

go get github.com/tracewayapp/traceway/backend

import tracewaybackend "github.com/tracewayapp/traceway/backend"

func main() {
    go tracewaybackend.Run(
        tracewaybackend.WithPort(8082),
        tracewaybackend.WithDefaultUser("admin@localhost.com", "admin"),
        tracewaybackend.WithDefaultProject("My App", "opentelemetry", "dev-token"),
    )

    // ... start your app, point its OTel exporter to http://localhost:8082/api/otel/v1/traces
}

Open http://localhost:8082, log in, and hit your app to see traces appear. Full walkthrough in the embedded mode guide, or check the working example.

Traceway integrates with the tools you already use. Every integration ships traces, metrics, and logs over OTLP/HTTP — no proprietary SDK required.

View the full list in the documentation. Missing a framework? Open an issue to request it.

Gin	Chi	Fiber	FastHTTP	net/http	Go Generic
Node.js	NestJS	Hono	Symfony	Cloudflare	OpenTelemetry

Session Replay is included with every frontend integration — and with Flutter too.

Next.js

React

Vue

Svelte

jQuery

JavaScript

Flutter

Android

React Native

OpenRouter

Logs — trace-linked search	Span waterfall
Metrics — application dashboard	Exceptions — grouped & ranked

# Embedded mode (SQLite, default)
cd backend && go build ./cmd/traceway

# Standalone server (ClickHouse + PostgreSQL)
cd backend && go build -tags pgch ./cmd/traceway

# SQLite tests (default, no tags needed)
cd backend && go test -v -count=1 ./app/repositories/

# ClickHouse + PostgreSQL tests (requires Docker)
./scripts/test-backend-pgch.sh

# OTEL trace converter tests (no DB required)
cd backend && go test -v -count=1 ./app/controllers/otelcontrollers/

# Update OTEL golden files after intentional converter changes
cd backend && go test -v -count=1 -args -update ./app/controllers/otelcontrollers/

Full documentation at docs.tracewayapp.com:

• Client SDKs — OpenTelemetry, Go, Node.js, Python, and more
• Self-Hosting — Docker Compose and production deployment
• Concepts — How tracing, exception grouping, metrics, and alerts work
• Embedded Mode — Run Traceway inside your Go app

Traceway is built in the open, and the Discord community is where it happens. Come say hi — whether you're kicking the tires, running it in production, or just curious. We use it to:

• 🗣️ Talk through ideas — feature requests, integration asks, roadmap input
• 🛟 Help each other out — setup, OTel wiring, deployment questions
• 🚀 Show & tell — share what you're building and how you're using Traceway
• 🐛 Catch bugs early — report issues and get fast feedback from maintainers
• 👀 Get the inside scoop — sneak peeks at what's shipping next

Contributions are welcome — pull requests get reviewed and merged. If you're not sure where to start or want to discuss an idea first, open an issue or drop by the community Discord and we'll talk it through.

• Website
• Documentation
• Traceway Cloud — managed hosting (same MIT code, run by us)
• Community Discord — chat with the team and other users