fanout
Single-binary observability platform. Ingest OTLP, store as Parquet, query with DuckDB.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/labstack/pitot with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/labstack/pitot'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/labstack--fanout)HTML
<a href="/listings/labstack--fanout"><img src="/api/listings/labstack--fanout/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
These steps run a script from the network that findsafeskills does not scan.
Docker
docker run --name fanout -p 7520:7520 \ -v fanout-data:/var/lib/fanout/data \ -e FANOUT_AUTH_CODE_SECRET=$(openssl rand -hex 32) \ labstack/fanout:latest
Open the one-time setup URL printed by the container and create the first administrator. Fanout displays the ingest token exactly once; save it with your collector secrets. For later sign-in without SMTP, mint a 15-minute, single-use link against the running container's control database:
docker exec fanout fanout login-link admin@example.com
The UI, API, MCP, and both OTLP transports share port `7520`. See [installation](https://fanout.run/start/install) for image defaults and bind-mount ownership, and [first boot](https://fanout.run/start/first-boot) for setup and SMTP login.
Native binary
Install a checksum-verified release for Linux or macOS, amd64 or arm64:
curl -fsSL https://raw.githubusercontent.com/labstack/fanout/main/scripts/install.sh | sh export FANOUT_AUTH_CODE_SECRET=$(openssl rand -hex 32) fanout
Set `FANOUT_VERSION=v2026.10.1-alpha` to pin a release and `FANOUT_PREFIX` to choose the installation directory. Native installs bind `127.0.0.1:7520`; set `FANOUT_ADDR=:7520` for remote access, then follow the same first-boot setup.
Send telemetry
A standard OTLP/HTTP exporter can use the saved ingest token:
export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:7520 export OTEL_EXPORTER_OTLP_HEADERS="authorization=Bearer%20$INGEST_TOKEN"
For a Collector on the same private container network, the forwarding side is:
exporters:
otlp_http/fanout:
endpoint: http://fanout:7520
headers:
Authorization: "Bearer ${env:INGEST_TOKEN}"
service:
pipelines:
traces: { receivers: [otlp], exporters: [otlp_http/fanout] }
metrics: { receivers: [otlp], exporters: [otlp_http/fanout] }
logs: { receivers: [otlp], exporters: [otlp_http/fanout] }Use an existing `otlp` receiver, set `INGEST_TOKEN`, and replace `fanout` with the Collector's reachable private hostname. OTLP/gRPC uses `localhost:7520` locally; see [send telemetry](https://fanout.run/start/send-telemetry) for TLS and HTTP/2 setup.
Enable chat
Select `FANOUT_AI_PROVIDER=anthropic` and inject `ANTHROPIC_API_KEY`, or select `FANOUT_AI_PROVIDER=openai` and inject `OPENAI_API_KEY`, then restart Fanout; the selected provider requires its key at startup. With no provider, chat is disabled and the other features still work. See [AI settings](https://fanout.run/reference/settings/ai).
Connect an MCP client
Set `FANOUT_PUBLIC_URL` to your stable, externally reachable HTTPS origin, then point a remote MCP client at that origin's `/mcp` endpoint. The client discovers and registers through OAuth; you authorize its scopes in the browser. The client must support MCP protocol `2026-07-28` over stateless Streamable HTTP; older versions and the `initialize` handshake are unsupported. See [connect over MCP](https://fanout.run/guides/connect-over-mcp) for setup and permissions.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 252 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- # Pitot
- Pitot (pronounced **PEE-toh**).
- **Observability your agents can operate.** Send OpenTelemetry to one binary, then investigate with
- Pitot's built-in agent or connect your own over MCP.
- [](https://github.com/labstack/pitot/actions/workflows/ci.yml)
- [](LICENSE)
- [](https://pkg.go.dev/github.com/labstack/pitot)
- <a href="https://pitot.dev">
- <picture>
- <source media="(prefers-color-scheme: dark)" srcset="site/src/assets/landing/overview-dark.png">
- <img src="site/src/assets/landing/overview-light.png" alt="Pitot Store overview - last hour: request rate, error rate, p95 latency and error logs, with request rate, error rate and p95 latency by service.">
- </picture>
- </a>
- *Current Pitot interface with deterministic offline sample telemetry.*
- Pitot keeps OpenTelemetry traces, logs, and metrics in one binary and one data directory, with no
- external storage services to operate. Pitot is pre-release and changes without migration paths; the browser
- client, built-in agent, MCP tools, dashboards, and alerts are preview capabilities
- ([status](https://pitot.dev/docs/reference/capabilities)). Start with the
- [documentation](https://pitot.dev) or run it below.
- - OTLP ingest over gRPC and HTTP, with local Parquet storage and DuckDB analytics.
- - Explore and PitotQL for querying telemetry without an AI provider.
- - An investigation agent that answers questions about your telemetry in plain language.
- - An MCP server for external agents using the same typed query tools.
- - Dashboards across traces, logs, and metrics, and alerts on service error rate, latency,
- throughput, and log volume.
- ## Quick start
- ### Docker
- ```sh
- docker run --name pitot --restart unless-stopped -p 7520:7520 \
- -v pitot-data:/var/lib/pitot/data \
- -e PITOT_AUTH_CODE_SECRET=$(openssl rand -hex 32) \
- labstack/pitot:latest
- ```
- Open the one-time setup URL printed by the container and create the first administrator. Pitot
- displays the ingest token exactly once, unless `PITOT_INGEST_TOKEN` already set it; save it with your collector secrets. For later sign-in
- without SMTP, mint a 15-minute, single-use link against the running container's control database:
- ```sh
- docker exec pitot pitot login-link admin@example.com
- ```
- The UI, API, MCP, and both OTLP transports share port `7520`. See
- [installation](https://pitot.dev/docs/get-started/install) for image defaults and bind-mount ownership, and
- [first boot](https://pitot.dev/docs/get-started/first-boot) for setup and SMTP login.
- ### Native binary
- Install a checksum-verified release for Linux or macOS, amd64 or arm64:
- ```sh
- curl -fsSL https://raw.githubusercontent.com/labstack/pitot/main/scripts/install.sh | sh
- export PITOT_AUTH_CODE_SECRET=$(openssl rand -hex 32)
- pitot
- ```
- Set `PITOT_VERSION` to a [release tag](https://github.com/labstack/pitot/releases), such as `v2026.11.0-alpha`, to pin a release, and `PITOT_PREFIX` to choose the installation
- directory. Native installs bind `127.0.0.1:7520`; set `PITOT_ADDR=:7520` for remote access, then
- follow the same first-boot setup.
- ### Send telemetry
- A standard OTLP/HTTP exporter can use the saved ingest token:
- ```sh
- export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
- export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:7520
- export OTEL_EXPORTER_OTLP_HEADERS="authorization=Bearer%20$INGEST_TOKEN"
- ```
- For a Collector on the same private container network, the forwarding side is:
- ```yaml
- exporters:
- otlp_http/pitot:
- endpoint: http://pitot:7520
- headers:
- Authorization: "Bearer ${env:INGEST_TOKEN}"
- service:
- pipelines:
- traces: { receivers: [otlp], exporters: [otlp_http/pitot] }
- metrics: { receivers: [otlp], exporters: [otlp_http/pitot] }
- logs: { receivers: [otlp], exporters: [otlp_http/pitot] }
- ```
- Use an existing `otlp` receiver, set `INGEST_TOKEN`, and replace `pitot` with the Collector's
- reachable private hostname. OTLP/gRPC uses `localhost:7520` locally; see [send
- telemetry](https://pitot.dev/docs/get-started/send-telemetry) for TLS and HTTP/2 setup.
- ### Enable chat
- Select `PITOT_AI_PROVIDER=anthropic` and inject `ANTHROPIC_API_KEY`, or select
- `PITOT_AI_PROVIDER=openai` and inject `OPENAI_API_KEY`, then restart Pitot; the selected provider
- requires its key at startup. With no provider, chat is disabled and the other features still work.
- See [AI settings](https://pitot.dev/docs/reference/configuration/ai).
- ### Connect an MCP client
- Set `PITOT_PUBLIC_URL` to your stable, externally reachable HTTPS origin, then point a remote MCP
- client at that origin's `/mcp` endpoint. The client discovers and registers through OAuth; you
- authorize its scopes in the browser. Pitot serves MCP `2026-07-28` and, through the `initialize`
- handshake, `2025-11-25` and `2025-06-18` over Streamable HTTP. See [connect over
- MCP](https://pitot.dev/docs/guides/mcp) for setup and permissions.
- ## How it compares
- | If you use | Where Pitot differs |
- | --- | --- |
- | **Grafana with Loki, Tempo, and Mimir** | That stack keeps a service and a query language per signal, plus object storage underneath. Pitot keeps one process, one data directory, and one typed contract across all three signals, at the cost of the horizontal scale those components are built for. |
- | **SigNoz** | Both are OTLP-native and self-hosted. SigNoz composes a collector, ClickHouse, and query services; Pitot compiles ingest, authoritative Parquet storage, indexed trace reads, DuckDB analytics, alerting, and the browser client into one binary. |
- | **Jaeger** | Jaeger covers traces and expects a storage backend you run separately. Pitot ingests traces, logs, and metrics into the same store, with nothing else to deploy. |
- | **Prometheus with Grafana** | Prometheus pulls metrics and is excellent at them. Pitot accepts pushed OTLP for all three signals and is built around investigating a specific incident rather than maintaining long-range metric series. |
- | **Datadog**, **Honeycomb**, **Grafana Cloud** | Those are managed services: someone else runs the storage, the scaling, and the upgrades, and your telemetry leaves your network to get there. Pitot is a binary you run, on data that stays on your disk. |
- | **An OpenTelemetry Collector piped into ClickHouse** | The same shape, assembled by hand: collector, database, dashboards, and the glue between them. Pitot is that assembly as one program, with an agent and an MCP server already wired to the same query contract. |
- Pitot is a single node. It has no clustering, no replication, and no object tier; a deployment that
- outgrows one machine's disk and CPU has outgrown Pitot.
- ## Architecture
- One process contains ingest, storage, query, alerts, the agent, MCP, and the React client. Browser
- and agent clients share a typed observability contract.
- 
- Parquet holds telemetry, DuckDB query state is rebuildable, and SQLite holds transactional product
- state. See [how storage works](https://pitot.dev/docs/concepts/storage) for durable ingest,
- indexed reads, and compaction while reads continue.
- 
- ## Configuration
- Configuration is environment-only: built-in defaults followed by nonempty process environment
- values, validated before data files or listeners open. Settings are read once at startup; every
- change requires a restart.
- | Environment variable | Default | Purpose |
- | --- | --- | --- |
- | `PITOT_ADDR` | `127.0.0.1:7520` | UI, API, MCP, and both OTLP transports |
- | `PITOT_DATA_DIR` | `./data` | Parquet, query state, and control SQLite |
- | `PITOT_AUTH_MODE` | `local` | Login link or SMTP, or `oidc` |
- | `PITOT_AUTH_CODE_SECRET` | — | Required in local mode and for OIDC break-glass links, 32+ characters |
- | `PITOT_AI_PROVIDER` | — | Empty disables chat; `anthropic` or `openai` enables it |
- | `ANTHROPIC_API_KEY` | — | Required for Anthropic chat |
- | `OPENAI_API_KEY` | — | Required for OpenAI chat |
- | `PITOT_RETENTION_DAYS` | `30` | Telemetry retention window |
- | `PITOT_MCP_ENABLED` | `true` | Serve the MCP endpoint at `/mcp` |
- Every secret accepts `<NAME>_FILE` instead of its value; see the [settings
- reference](https://pitot.dev/docs/reference/configuration) for validation and [runtime secret
- delivery](docs/operations.md#runtime-secret-delivery) for deployment examples.
- ### Advanced DuckDB sizing
- Pitot sizes DuckDB automatically; measured workloads can override memory, connections, and threads
- as described in [DuckDB sizing](https://pitot.dev/docs/reference/configuration#duckdb-sizing).
- For TLS, health checks, backups, upgrades, retention, and recovery, see the [operator
- runbook](docs/operations.md).
- ## Performance
- Pitot v2026.11.0-alpha accepted **507,311 mixed OpenTelemetry items/s**
- over 306.8 seconds on a Hetzner Cloud ccx33 (8 dedicated vCPUs, 32 GB RAM), with
- telemetrygen on a separate ccx33. The ingest run on 6 November 2026 passed every
- quality gate. See the [performance methodology](https://pitot.dev/docs/concepts/performance).
- [Pitot Bench](https://github.com/labstack/pitot-bench) reproduces the measurement on your hardware.
- ## Build from source
- - **Go 1.27.3 and a C/C++ toolchain** on native Linux or macOS, amd64 or arm64.
- Build with `just build` or `bash scripts/with-duckdb.sh go build ./cmd/pitot`;
- the wrapper supplies DuckDB's pinned headers, static libraries, and CGO flags.
- The first build needs network access to download the checksum-verified engine.
- - **[Bun](https://bun.sh)** — compiles the browser assets
- - **Node.js 24.19.0** — runs development helpers and builds the documentation site
- - **[just](https://just.systems)** — task runner
- - A 32-character **authentication code secret**
- ```sh
- git clone https://github.com/labstack/pitot.git
- cd pitot
- just install # browser dependencies and git hooks
- just build # browser assets, then the binary
- ```
- Run it with the minimum configuration:
- ```sh
- export PITOT_AUTH_CODE_SECRET=$(openssl rand -hex 32) # must be 32+ characters
- ./bin/pitot
- ```
- Open <http://localhost:7520> and follow first-boot setup. SMTP and chat are optional; without SMTP,
- run `./bin/pitot login-link admin@example.com` with the same configuration and data directory.
- ## Development
- Run `just` to list recipes, `just check` for the full gate, `just test` for Go tests, and `just ui`
- to rebuild embedded browser assets. See [CONTRIBUTING.md](CONTRIBUTING.md) for environment setup,
- generated assets, hooks, and project layout.
- ## Releases
- Versions are CalVer — `vYYYY.M.N[-alpha|-beta|-rc]`, numbered from 0 within each month across all
- maturity suffixes. Pitot is alpha (for example, `v2026.11.0-alpha`); GA has no suffix.
- Container tags omit the leading `v`, and every release moves `latest`. Tagged releases publish
- identical manifests to Docker Hub (`labstack/pitot`) and GHCR (`ghcr.io/labstack/pitot`); GHCR is
- canonical and also carries development images.
- | Image tag | Points at |
- | --- | --- |
- | `labstack/pitot:latest` | the newest release, mirrored on Docker Hub |
- | `labstack/pitot:2026.11.0-alpha` | that exact release, mirrored on Docker Hub |
- | `ghcr.io/labstack/pitot:latest` | the newest release |
- | `ghcr.io/labstack/pitot:2026.11.0-alpha` | that exact release |
- | `ghcr.io/labstack/pitot:main` | the tip of `main` |
- | `ghcr.io/labstack/pitot:sha-<commit>` | one specific commit |
- See [docs/release.md](docs/release.md) for platforms, checksums, provenance, and verification.
- ## Contributing
- Issues and pull requests are welcome; follow [CONTRIBUTING.md](CONTRIBUTING.md) and run `just check`
- and `just test-race` before opening a pull request. Report security issues through
- [SECURITY.md](SECURITY.md).
- ## Scope
- This repository builds Pitot without another repository; LabStack's deployment configuration,
- uptime monitoring, and public demo instance are not included. The documentation site in
- [`site/`](site) is included, with settings pages generated from the same `internal/config` type the
- loader binds and checked by `just check`.
- ## License
- [Apache-2.0](LICENSE) © LabStack LLC. See [NOTICE](NOTICE) and
- [THIRD_PARTY_NOTICES](THIRD_PARTY_NOTICES) for attribution, and
- [TRADEMARK](TRADEMARK.md) for use of the Pitot name and logo.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.