in production at
supergood.aitrymemorylane.com
what it does
no browsers, no human solvers, no external vendors in the loop. we run the challenge inside our own sandbox and generate the payload directly — your worker calls the container on localhost and gets a valid token back.
vendor updates
don't take you down
"what happens when akamai changes something?" is the question everyone asks. the answer is that our tooling discovers the change and patches the solver — that loop is the product.
nothing leaves
your network
every other option means shipping your customers' requests, cookies and tokens to someone else's api — the thing enterprise security reviews stop. xhr.dev runs on your side of the boundary, and works with outbound internet turned off entirely.
deployment docsREQUEST PATH
01
your worker
02
xhr.dev container
03
target site
✓ no external solving api
✓ works with egress disabled
questions
our tooling auto-discovers the change against the live challenge and patches the solver, then pushes a new image to your registry. you pull it — no work on your side, no waiting for a human to reverse-engineer it from scratch.
run the container and point your code at it over http. it returns a token you attach to the request you were already making.
no. we don't resell another solver or route through anyone else's api — the sandbox and payload generators are ours, running on your hardware.
yes — several teams run us as a second solver for redundancy, and fail over when their primary gets blocked.
yes. it needs no outbound internet to solve. updates are images you pull on your own schedule.
a docker host. it's stateless, so you scale it out the same way you scale your workers.
no. solving happens inside your own network. we never proxy, store or log your requests.
a flat fee, unlimited solves — no per-request or per-gb billing. book a call and we'll give you a number for the vendors you need.
see it running in your stack
20 minutes with the engineers who build it.