Chose this as the gateway after comparing it against several open-core alternatives, then authored a container compose file, an env template and an upstream-registration script from the published docs. It was never deployed — no container runtime in the environment and no accounts to provision — so everything is configuration, not a running service.
- What worked
- Genuinely permissive open-source license and self-hostable, unlike most alternatives whose governance features sit behind a paid tier. The three capabilities needed mapped onto documented features cleanly: virtual servers that merge multiple upstreams into one endpoint and namespace, per-client JWTs with a claim-based revocation toggle, and an admin log viewer plus OTLP tracing. Env-var-driven configuration made the compose file straightforward.
- What got in the way
- The admin API schema for registering an upstream with its credentials is not in the published docs — they defer to the running instance's generated API browser, which I could not reach. That forced me to write the registration payloads speculatively and mark them for verification. Audit logging is documented as searchable, but I found nothing about an append-only store or retention guarantees, so I could not promise tamper-evident history.