Design partners
Test Waymesh against your real AI workloads.
We are accepting a limited number of design partners. The evaluation runs in shadow mode against your production traffic and changes nothing about what executes — you get a measurement of your own stack either way.
Fit
Who this produces a useful answer for.
Routing only pays off where there is a real choice to make. These are the conditions under which an evaluation tells you something you could not have guessed.
AI-native SaaS
Model calls are in your product's critical path, not a side feature. When a provider degrades, your users notice before your dashboard does.
Meaningful model and API usage
Enough volume that routing decisions compound. A few hundred calls a month will not produce evidence worth acting on; sustained production traffic will.
Multiple providers, or growing complexity
You already run more than one model or provider, or you are accumulating the conditionals that mean you are about to. Either way the routing logic has started to live in your application.
An engineering team that cares about the numbers
Someone owns cost and performance and would act on a measured result. Design partnership is a working relationship, not a pilot that runs unattended.
If your workloads all have one sensible route, routing has nothing to offer you and we would rather establish that in the first conversation than at the end of an evaluation.
Process
Six steps, and what each one costs you.
Workload discovery
We go through the workloads you actually run: shape, volume, constraints, what a failure costs, and which of them have real routing alternatives. Some workloads have one sensible route, and we would rather say so early.
One session
Integration
Waymesh is placed alongside your existing path, not in front of it. Requests are submitted with their requirements; your current routing keeps control of what executes.
Engineering time on your side, scoped in discovery
Shadow evaluation
For every request, Waymesh decides and records the route it would have chosen. Nothing about your execution changes. This is the stage that produces the evidence.
Runs in the background
Measurement
Predictions are checked against what the executed route actually cost and took. Disagreements between the two routers are counted rather than averaged away.
Continuous
Review
We go through the record together: where the routers agreed, where they did not, what the alternative would have cost, and which segments have enough evidence to say anything at all.
One session
Optional production rollout
If the evidence supports it, routing takes authority — for the segments the evidence covers, and no further. If it does not, you have a measurement of your own stack and owe us nothing.
Your decision
Measurement
What you get back.
Measured on your traffic, over the evaluation window, at the granularity routing decisions are actually made at.
- Cost
- Predicted cost per request against what was actually settled, per provider and per workload type.
- Latency
- Observed end-to-end time on the route that ran, held separately by task type rather than blended into one average.
- Reliability
- Success rate by provider and workload, carried with its uncertainty so a thin sample is not mistaken for a strong one.
- Routing disagreements
- How often Waymesh would have chosen differently from your current path, and which route it preferred.
- Provider utilization
- Traffic and spend distribution across providers — including whether the provider carrying the most requests is the one carrying the most cost.
We do not promise a savings percentage. We have not measured your workloads, and any figure quoted before that would be invented — which is the opposite of what this evaluation is for. The output is a measurement of your stack, and it is entirely possible the answer is that your current routing is already right.
Apply for design partner access.
Applying creates your Waymesh account. We follow up to arrange discovery, where we go through the workloads you run, roughly what volume, and which constraints are non-negotiable.
No workload details are collected at this step, and nothing runs against your traffic until discovery has scoped it with you.