Your API operation runs on vendors — the gateway, the management platform, the documentation tool, the testing service, the monitoring system — and the accumulated choices determine how flexible, how expensive and how portable your operation is. These are strategic decisions that usually get made tactically.
The rule that protects you: your source of truth lives in open formats in your own repositories. OpenAPI, AsyncAPI, JSON Schema, Spectral rules, collections in a portable format, all in Git. Vendors consume those artifacts and do something useful with them. The moment your contracts only exist inside a vendor’s database and can only be edited in their UI, you have handed over the thing that makes you portable.
Buy for execution, not for custody. A gateway that configures itself from your OpenAPI is replaceable. A gateway that is the only place your routes are described is not.
Before signing, ask the exit questions out loud: how do I get my definitions out, in what format, and what breaks when I do? If the honest answer is “an export that loses half the metadata,” price that in.
And expect consolidation. The vendor landscape has been merging and unbundling in cycles for fifteen years, and the platform you standardize on today has a real chance of being acquired. Portability is not paranoia; it is the base rate.
