Compare full API management platforms across AWS API Gateway, Azure APIM, Apigee, and OCI API Gateway.
Output will appear here...The comparison table is a static, hand-maintained dataset of feature rows grouped by category (overview, security, developer, pricing, performance) with free-text search across all fields; it's a reference snapshot, not a live specs feed, verify current pricing tiers and feature availability directly with the provider before an API platform selection decision.
A comparison of full API management platforms across Amazon API Gateway/AppSync, Azure API Management (APIM), GCP Apigee, and OCI API Gateway, and the pricing gap between the entry-level and full-featured tiers is dramatic: Apigee's Standard tier runs roughly $6,600/month and Enterprise roughly $12,500/month, while Azure APIM's Consumption tier starts at $3.50/million calls and OCI charges a flat $3/million calls with no platform subscription fee at all, meaning Apigee is priced for large enterprise API programs, not a good fit for a small team's handful of APIs regardless of its feature depth.
Comparing sticker-price-per-million-calls across these four without factoring in Apigee's flat monthly platform fee produces a misleading cost picture, Apigee's platform fee alone can exceed what OCI or Azure Consumption tier would charge for the same call volume by a wide margin.
OCI's lack of a native developer portal is often discovered late in a proof-of-concept, if external developer self-service (API key signup, docs, sandbox testing) matters, validate this gap exists before committing rather than assuming it's a minor console feature difference.
Request/response transformation capability (VTL, XSLT, custom JS/Python/Java policies) varies enough in expressiveness that a complex existing transformation layer may not port cleanly to OCI's more limited header/query-param rewriting, audit actual transformation logic complexity before assuming a lift-and-shift migration.
It's genuinely absent as a built-in feature, unlike AWS, Azure, and GCP which all ship some form of developer portal (a Serverless Application Repository-based portal for AWS, a fully customizable built-in one for Azure, a Drupal-based one for GCP Apigee). If a self-service developer portal is a requirement, OCI API Gateway needs a custom-built portal via its API catalog, that's real additional engineering effort to budget for.
Apigee is positioned as an enterprise API management platform with deep analytics, monetization, and governance features aimed at large-scale API programs managing many partner/customer integrations, not a basic API gateway. Its Standard ($6,600/mo) and Enterprise ($12,500/mo) tiers reflect that positioning; for a team just needing rate limiting and auth in front of a handful of backend services, this is likely the wrong product regardless of GCP being the primary cloud, a lighter option or even GCP's own more basic Cloud Endpoints may fit better.
Not equally, Azure APIM has native GraphQL support, AWS supports it via a separate product (AppSync, not API Gateway itself), GCP Apigee supports GraphQL API proxying, and OCI API Gateway is REST-only with no GraphQL support. If GraphQL is a requirement and you're evaluating OCI, that's a hard gap, not a configuration difference.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.