The operating problem
Gateway replacement fails when configuration translation is treated as a file conversion instead of an operational change with hidden policies, credentials, traffic behavior, and rollback risk.
The intended control surface
This capability is part of the reviewed product architecture, not a decorative console module.
- Versioned vendor-neutral migration IR
- Compatibility findings with confidence and manual actions
- Sandbox deployment and replay
- Canary cutover with rollback checkpoint
What exists today
OpenAPI source retention, normalized operations, scoped upstreams and routes, signed snapshots, and rollback provide the destination foundation. No Kong, Apigee, MuleSoft, Layer7, AWS, Azure, Tyk, or Gravitee importer is currently available.
Work with the implementation team
Reallexi is accepting architecture conversations with teams whose requirements can shape this production slice. An inquiry does not imply that an unshipped feature is available.
Frequently asked questions
Is this capability generally available?
No. The page describes a reviewed implementation direction. The current capability boundary is stated above and in the public changelog.
Can Reallexi evaluate our requirements?
Yes. Use the enterprise inquiry form without including credentials, private payloads, or regulated data.