API Gateway across clouds
Managed API front doors - routing, authentication, throttling and quotas in front of your services, as verified modules.
5 verified modules, 4 of them live-tested apply→verify→destroy; the rest are static-validated, live-test pending.
Compare by provider
| Provider | Module | Verification |
|---|---|---|
| AWS | API Gateway HTTP API | ✓ live-tested |
| AWS | API Gateway REST API (deny-by-default) | ✓ live-tested |
| Azure | API Management (Consumption tier) | ✓ live-tested |
| Google Cloud | API Gateway (OpenAPI 2.0) | ✓ live-tested |
| Oracle Cloud | API Gateway & Deployment | static-validated |
How to choose
Match the protocol you actually serve first (plain HTTP versus REST-with-a-lifecycle versus gRPC), then decide whether you need a full API product - developer portal, versioning, monetisation - or only a router with auth. The lightweight HTTP tiers cost a fraction of the management-suite tiers and cover most services.
When not to use
With one service behind it and an ingress or load balancer already in front, an API gateway is an extra hop and an extra bill for routing you are doing twice.
Other solutions
Managed Relational Database18Managed Kubernetes15Virtual Machines13Messaging & Pub/Sub11Load Balancer10DNS & Traffic Management10Virtual Private Cloud (VPC)9Serverless Containers7Secrets & Key Management7Serverless Functions6Object Storage5Identity & Access5Container Registry3CDN & Edge Delivery3In-Memory Cache3Monitoring & Observability3WAF & Edge Security3Shared File Storage3