Logs. Vectors. Agent memory. One Rust engine instead of three glued systems. This page shows the product — real dashboard visualizations on seeded data, measured numbers against Elasticsearch 8.13, and the engine internals that make the numbers possible.
The visualizations below are not illustrations. They're the real dashboard components rendered on seeded mock data so you can see what the product looks like before a single config line. Drop a work email if you want a private binary and the reproduction scripts for the benchmark tables.
XERJ rejects the Kibana aesthetic — boxed visualizations, shadowed cards, icon-heavy toolbars. Every screen is typography, negative space, and 1 px lines. Every chart below is the same component that runs in the dashboards — same code, same rules, same restraint.
Five models, 60 seconds. Depth encodes model generation — OPUS at the front, HAIKU at the back. Every stroke is a 1 px line.
Every query is a point in 1536-dimensional space. The dashboard projects them down to 2D and colors the six most common intents. Fresh queries appear as hollow marks; old ones fade. This is the EmbedSpace primitive — you get it by wiring a dense vector field to the field catalog, no additional config.
Traces aren't a separate product — they're a graph query on the logs index. The ChordArcs primitive renders service → index flows as a text-first sankey. Traffic is real rps; no icon waterfall. Drill through any edge to the underlying spans.
Twelve recent queries across six dimensions. Drag a handle on any axis in the live version to filter. The dashboard highlights queries whose recall@10 falls below a threshold — this is how you find the cases your retrieval is failing on.
When a RAG pipeline misses, the first question is "did the model even look at the right words?" XERJ's attention overlay marks the retrieved passage with per-token weight. Accent-yellow tokens are the top 20 % by attention weight. No heat tiles, no color ramp — just opacity.
Context windows are big and boring. XERJ visualizes the budget as a left-to-right flow: system prompt, context, question, completion. Width encodes tokens. You spot a bloated context in a glance.
Every dashboard still needs a top-N, a distribution, and a heatmap. XERJ ships them as the same 1 px primitives the rest of the visuals are built from — same code, same rules, different shapes.
Every row below comes from a dated, checked-in battle report in the engine repository. No synthetic micro-benchmarks, no hand-picked best run — the reports include repro scripts and hardware profiles. Where ES shards its cluster across 4 nodes, we run XERJ on 1. The caveats are published alongside the wins.
Speed is not one trick. XERJ is fast because everything happens in one process, in one language, against data laid out exactly the way the queries want to read it. Below are the six choices that account for most of the delta.