Open control plane

Spanport

Route swarms without rewiring.

One OTLP key. Policy fan-out to your Langfuse, Phoenix, or generic backends — built for agents that call other agents.

Start freeView docs

Instrument once. Land where you debug.

Spanport is the pipe, not another tracer UI. Spans pass through auth, swarm-aware policy, and dual-write — then leave.

  1. Ingest OTLPJSON or protobuf on the gateway. Preserve traceparent and baggage across swarm handoffs.
  2. Match swarm.* / agent.* / handoff.*Route by fleet identity. Redact content before peer-org destinations when you need shared correlation, split payloads.
  3. Fan out to BYO backendsIsolated queues retry failures without blocking siblings. Meter usage; destinations stay the debugger of record.

Your backends. Our routing.

Keep Langfuse for prod, Phoenix for eval, Tempo when you only need the graph — same instrumentation.

langfuse · phoenix · braintrust · otlp_generic → tempo / honeycomb / grafana

Built for swarm ↔ swarm.

When fleets call fleets, trees lie. Spanport correlates handoffs without merging payload ownership across trust boundaries.

The peer-pipe idea — a dedicated corridor between swarms — lives as product vocabulary (and reserved Peerpipe domains). The company brand stays Spanport.