no moreanti-bot blocks.
no more
anti-bot blocks.solvers for the hardest challenges. still working after the vendor's next update.
your infrastructure
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.
milliseconds, not seconds
we solve at the payload level. no playwright instance to spin up, no cpu and ram burned per challenge.
runs in your infra
a docker image on your own hosts. no third-party api call, so nothing to explain in a security review.
flat fee, unlimited solves
no per-request or per-gb billing at any volume. one number, whatever your traffic does.
supported today
datadomeakamai bot manager
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.
our tooling finds the change
we watch the live challenges continuously. when a vendor ships new logic, the tooling auto-discovers what changed — we're not waiting on your bug report.
it patches the solver
the fix is generated and tested automatically, then a new image goes to your private registry. you pull it and carry on.
built to survive minor updates
we solve the challenge vm itself, not individual scripts, so most vendor changes never reach you in the first place.
nothing leaves
your networkevery 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.
REQUEST PATH
01
your worker
02
xhr.dev container
03
target site
✓ no external solving api
✓ works with egress disabled
questions
how do you update a solver when a vendor breaks it?−
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.
how do we integrate it?+
do you depend on any external solving vendors?+
can we run it alongside our current setup?+
can we run it air-gapped?+
what does it need to run?+
do you see our traffic?+
what does it cost?+
see it running in your stack
20 minutes with the engineers who build it.