Prove the savings on your own data.
BV‑SALA sits in front of any LLM provider and, for every request, picks the cheapest execution that still meets your quality bar. Don't take our word for it — paste your data below and watch the meter move.
Try the optimizer yourself. Nothing leaves this page.
These two instruments run the real optimizer locally so you can sanity-check the mechanism before touching a provider. The left panel runs the actual format selector on data you paste — real token accounting, the same code the SDK ships. The right panel estimates a monthly bill by running the optimizer over a sample workload against a mock model. For provably-measured dollars, see Step 2 below.
Encode your payload for less
Paste any JSON. We count tokens for compact JSON, TOON and CSV and pick the cheapest — including the instruction overhead each format needs.
Project your monthly bill
Enter your real traffic. The projection compounds call‑avoidance, context reduction and output restriction — the levers multiply, they don't add.
Real savings, measured against a real provider. Both arms.
This is the output of the A/B benchmark (pnpm ab): for every scenario it sends a naive request and the BV‑SALA request to the same model, prices both from the provider's own token usage, and reports the 95% confidence lower bound — never the flattering point estimate. Nothing is modeled.
Four separate ledgers. Never summed into one vanity number.
A cache hit removes a whole call. TOON re‑encodes structured data. Compression drops redundant words. A provider prefix cache makes tokens cheaper without removing them. Mixing them lies to you — so we don't.
avoided_calls
LLM, retrieval and tool calls that never executed at all.
eliminated_tokens
Information dropped because it simply wasn't needed.
compressed_tokens
Information kept, but encoded with fewer tokens.
provider_cached_tokens
Still in the prompt, but billed or processed more cheaply.
Self‑host free. Your prompts never touch our servers.
Drop the SDK in front of your provider. Every response carries a full SavingsReport you can chart — the same numbers the dashboard reads.
// your app — the data plane. LLM traffic goes straight to your provider. import { createSavingsLayer } from "@bivelio/savings-layer"; const layer = createSavingsLayer({ provider: yourProvider }); const { data, report } = await layer.generate({ model: "openai/gpt-4o-mini", messages, response: { contractId: "answer:v1", schema, maxOutputTokens: 220 }, }); report.cost.netSavings; // → 0.59 (verified, per request) report.calls.avoidedLlm; // → whole calls you never paid for
Pennies to run. Multiples to save.
Free, capped, self‑hosted forever. Unlock the managed brain — semantic cache, learned thresholds, dashboards — per seat.
Pro · billed per active seat. Metered and value‑based plans for scale.
- Everything in Free, uncapped
- Managed semantic cache & learned thresholds
- Savings dashboards & team analytics
- EU data residency · your prompts stay on your infra
Why the price can be this low
- We move no tokens. Your LLM traffic flows straight to your provider — we only see counts, never content.
- You self‑host the heavy part. The optimizer runs in your process; our servers just license, learn and report.
- Infra scales with revenue. It starts on one small box and only grows once paying customers cover the next tier.
- The report is the meter. Billing reads the same SavingsReport you verify above — no black box.