Moving routes, authentication and traffic policies into APISIX from Ingress NGINX, plain NGINX and other open-source gateways, with parallel running and rollback.
Replacing the retired Ingress NGINX controller with the APISIX Ingress Controller: inventorying Ingress resources and annotations, mapping them to Ingress v1, Gateway API or APISIX CRDs, running both controllers side by side and switching traffic.
Moving hand-written NGINX reverse proxy configuration to APISIX: translating server and location blocks into routes and upstreams, replacing reload-based changes with the Admin API or ADC, and porting auth, limits and rewrites to plugins.
Moving a self-managed Kong Gateway to APISIX: mapping services, routes, consumers and plugins, key and JWT credentials, rate limiting counters, custom Lua plugins, and a canary cutover with traffic-split.
Moving APIs from Tyk Gateway to APISIX: API definitions to routes and services, keys and policies to consumers and limits, Go and Python middleware to plugin runners, and parallel running during the move.
Replacing the WSO2 API Manager gateway with APISIX: which lifecycle and portal functions need another home, mapping throttling policies and OAuth validation, and moving APIs group by group.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.