The Spanloom Platform

Complete LLM observability
in one dashboard

Four focused modules that cover everything from a single request trace to fleet-wide cost trends. No extra infrastructure, no separate logging pipeline.

Module 01

Trace Waterfall

Every LLM request becomes a structured trace with child spans for retrieval, embedding, model calls, and output parsing. The waterfall view shows duration, tokens, and cost at each step.

  • OpenTelemetry-compatible span model
  • Nested spans for chained and multi-agent workflows
  • Per-span token counts and latency attribution
  • Filter by trace ID, model, or custom metadata
Trace: rag_answer #b7d1e9
rag_answer root 2.1s
  embed_query 210ms 220tok
  vector_search 88ms top_k=5
  rerank 44ms
  llm_complete 1.7s in=2840 out=412
    tool_call: get_doc 120ms
  output_parse 18ms
Module 02

Token Cost Monitoring

Attribute token spend to every user, endpoint, model, and request path. Know your cost per feature before the monthly invoice arrives.

  • Per-request cost breakdown across input and output tokens
  • Model-level spend comparison in a single view
  • Daily and monthly trend charts with anomaly flags
  • Budget alert thresholds via webhook or email
Cost explorer - last 7 days
Endpoint Model Requests Cost
/chat/answergpt-4o4,821$48.21
/summarizeclaude-3.51,203$12.47
/classifygpt-4o-mini9,112$4.08
/embedtext-embed-322,400$0.90
Total$65.66
Module 03

Prompt Drift Detection

Prompt text changes silently through iterations, A/B tests, and rushed hotfixes. Spanloom tracks every prompt version hash and alerts when the live version diverges from your declared baseline.

  • Automatic prompt fingerprinting per request
  • Version timeline with diff view between versions
  • Drift alert triggers: hash change, token count change, semantic distance
  • Rollback annotations to mark which version is canonical
Prompt versions: system_prompt_v3
v3.1 ACTIVE  hash:a8f3c2  Jul 2
+ "Always cite sources in [brackets]."
- "Respond concisely."
v3.0 DRIFT  hash:d2b1e4  Jun 28
tokens: 1,240 (was 1,180)
alert fired: 2026-06-28T14:22Z
v2.9 BASELINE hash:c9a0f7 Jun 12
Module 04

RAG Retrieval Auditing

When a RAG pipeline fails, the problem is almost always in retrieval. Spanloom shows which chunks were fetched, their relevance scores, and whether they ended up influencing the answer.

  • Per-request chunk inspection with relevance scores
  • Context utilization rate (how much of the context window was used)
  • Dead-chunk detection: retrieved but not cited in output
  • k-value and threshold tuning recommendations
Retrieval audit - trace #a8f3c2
ChunkScoreTokensUsed
doc_42 p.30.91312yes
doc_17 p.10.87280yes
doc_88 p.50.72195yes
doc_55 p.20.58401no
doc_03 p.70.51388no
789 tokens fetched but unused (40% waste)
Get Started

Instrument your first pipeline today

Free during early access. No credit card required. Working traces in under five minutes.

Start Free Trial