Migration guides
Moving an existing stack onto INFRO
One guide per product, written from that product’s own published documentation with the sources and dates printed at the foot. Each one maps the concepts across, shows the code that changes, states plainly what does not come across — and names the case where a different product is the better destination.
INFRO is in private early access. The catalog, the docs, and the API contract are public today, and the gateway is deployed. The console opens with an early-access account, billing opens in stages, and anything beyond v1 is marked Later. Early access details
From Cloudflare AI Gateway
Generally available; core features freeMost readers should stay
Nothing is forcing this one, so the guide opens with three numbers to measure on your own gateway — two of which end the decision in Cloudflare's favour. Then the mapping: headers become a body field, retry headers have nowhere to go, the response cache matches exact chat completion requests only, and safety-category guardrails and Workers AI have no equivalent here at all.
Read the guideFrom Helicone
Acquired by Mintlify; services in maintenance modeLangfuse is often the answer
The gateway integration maps almost directly; the annotations move from request headers into the request body, and the response cache matches exact requests only. Prompt management, evaluators and semantic caching have no equivalent here, self-hosting needs an enterprise agreement, and the guide says where to go instead.
Read the guide
Running something else and wondering whether the move is worth it? Tell us what you have. If the answer is that you should stay where you are, that is the answer you will get.