90 days of the enterprise, pro and team plans free, no card needed. See the plans
A 2-4 week pilot
A pilot has a baseline agreed up front, success criteria the product measures itself and a date for the readout. One week in shadow, one on a canary share, then the ramp - and at the end the savings report, the quality evidence and the policy evidence are already in the dashboard.
No card for the trial. Prefer to read first? The savings calculator turns last month's bill into the business case.
Week by week
Week 0
Finance signs the baseline - your current model for all pilot traffic, or the real 30-day mix from last month's bill. The catalogue and the rules are reviewed together; the quality floor goes into the policy.
Upload last month's billWeek 1
The router answers every live request a second time, beside the policy in force, and nothing is served from it. You read the agreement, the spend delta and where traffic would move - before a single answer changes.
How shadow routing readsWeek 2
A share of the application moves to model="auto" or /v1/route. Outcomes flow back through /feedback so the learners warm on your traffic, and the savings page shows the baseline against the routed cost per request.
The savings pageWeeks 3-4
The canary grows, the quality gate you kept keeps running, drift and calibration are checked, and the readout is the product's own numbers: the savings report, the outcome scores, the policy rejections and the hash-chained audit log.
The governance reportSuccess criteria
The pilot passes when the four below are met - or the policy and operations ones alone, when compliance is the reason you are routing.
Cost
At least 30 % below the baseline on pilot traffic - read from the savings ledger, per request, never from a slide.
Quality
Outcome scores within two points of the baseline and no quality-floor violation - the outcomes in the ledger and a labelled sample routed as an evaluation.
Policy
Every PII- or region-constrained request on a compliant target - the trace's rejections and the audit trail are the evidence.
Operations
Routing decisions under 10 ms at p99 and no incident attributable to the router - the health and metrics pages.
