A/B Testing
Split live traffic between two versions to compare them on real usage — with live stats on runs, latency, error rate, and cost.
How it works
Start an A/B test by choosing two versions (variant A and variant B) and a traffic split for B. When an inference call resolves to the prod/live version that matches variant A, the test randomly routes a share of that traffic to variant B instead.
- One active test per prompt (and per chain) at a time — enforced in app logic and by a database constraint.
- Traffic split — set the probability that a request is routed to variant B.
- Live stats — runs, error rate, latency, and cost for each variant, computed from logged runs within the test's time window.
Lifecycle
1
Start
Pick variants A and B and a split, then start the test from the History/Versions tab.
2
Observe
Watch variant stats accumulate as real traffic flows through both versions.
3
Stop & promote
Stop the test, then deploy the winning version to prod.
Chains too
Chains have the exact same A/B testing flow as prompts. See Prompt Chains.