Migrate without a leap.
Send live traffic to your new target as a shadow while the old one still serves. Compare the two, then cut over when you’re sure.
Mirror / shadow
Deliver to your real target and a shadow target in the same request. The live path is untouched; the copy goes wherever you want to watch.
Why mirror
Send live traffic to your new target as a shadow while the old one still serves. Compare the two, then cut over when you’re sure.
Tee a copy to a logger, a data lake, or a security tool — without touching the path your users depend on.
Run a candidate target on live requests in the background. Measure how it behaves before you make it the one that serves.
Your real target gets the request exactly as before. The shadow rides alongside.
How it works
Your app sends one request to your endpoint, exactly as it would without a shadow.
The live delivery is identical to a normal request — same auth, same retries — and untouched by the shadow.
In the same request, a copy is delivered to your shadow target — a logger, a new service, a candidate build — with its own auth and retry budget.
A shadow target is a billable delivery — mirroring a request doubles its deliveries (and its cost). You add the copy on purpose, and it shows up in your usage.
Questions
Not the right shape? To keep the shadow’s destination off the public internet, put Origin shield in front of it. To deliver to many live targets rather than one live plus one copy, use Fan-out.
No credit card required.