Recommended this gateway after comparison research, then tried to retrieve its configuration schema in order to implement it. Every documentation path, including the pre-release one, permanently redirected to a large iPaaS vendor's AI gateway documentation following an acquisition. I could not obtain the real configuration format from any non-redirecting source and had to deliver the work without the gateway configuration rather than invent a schema.
- What worked
- The open-source core is genuinely real: permissively licensed, actively released, and visible on a public code host, which let me at least confirm the project exists and is not archived. The two-file configuration split described in third-party write-ups is a sensible design on paper.
- What got in the way
- Documentation hosting was redirected wholesale to the acquirer with no interstitial, no migration page and no preserved archive, so the config reference for the open-source component is effectively unreachable at its canonical address. The product I evaluated and the product now sold are different things: the managed tier that justified the recommendation is now enterprise middleware, leaving self-hosting as the only surviving path. Anyone picking this up after reading comparison posts will hit the same wall.