Self-Hosted vs Managed API Gateway: True Cost Comparison
Running Kong OSS or Traefik on Kubernetes can eliminate per-request charges, but adds infrastructure costs and significant engineering overhead. Here is an honest cost analysis at different traffic volumes, including the engineering time most comparisons ignore.
The hidden cost of self-hosting
Most cost comparisons only count cloud infrastructure. The real cost of self-hosting an API gateway is 8 to 16 hours of engineering time per month for maintenance, security updates, capacity planning, and incident response. At a fully-loaded engineer cost of $100/hour, that is $9,600 to $19,200 per year in engineering overhead before you factor in infrastructure.
Monthly Cost Comparison by Volume
| Solution | Type | At 10M req/mo | At 100M req/mo | At 500M req/mo | Eng. Time |
|---|---|---|---|---|---|
| Managed (infrastructure + request fees) | |||||
| AWS API Gateway | Managed | $35 | $280 | $900 | ~2 hrs/month |
| Cloudflare API Gateway | Managed | $3 | $20 | $55 | ~2 hrs/month |
| Kong Konnect | Managed SaaS | $9 | $54 | $175 | ~4 hrs/month |
| Self-hosted (infrastructure only, excludes engineering time) | |||||
Kong OSS (Kubernetes) 3x m5.large nodes, NLB, persistent storage, monitoring | Self-hosted | $250 | $350 | $600 | 8-16 hrs/month |
Traefik OSS (Kubernetes) 2x m5.xlarge nodes, NLB, Prometheus/Grafana stack | Self-hosted | $200 | $280 | $450 | 6-12 hrs/month |
NGINX Plus (VMs) NGINX Plus license $3,500/year + 2x c5.xlarge + ALB | Self-hosted | $450 | $500 | $700 | 10-20 hrs/month |
Break-Even Analysis
Low traffic (10M req/mo)
Use managed. Self-hosted costs 10x more.
Medium traffic (100M req/mo)
Cloudflare wins at this volume. AWS approaches break-even with Kong OSS.
High traffic (500M req/mo)
Self-hosted can beat AWS at this volume. Cloudflare still wins outright.
Very high traffic (1B+ req/mo)
Self-hosted vs AWS: worth evaluating. Cloudflare still competitive.
Annual Engineering Overhead for Self-Hosted Gateways
Based on a fully-loaded engineer cost of $100/hour. These costs apply regardless of traffic volume.
| Engineering Task | Time Estimate | Annual Cost ($100/hr) |
|---|---|---|
| Initial setup and configuration | 40-80 hrs | $4,000-8,000 |
| Ongoing maintenance and upgrades | 8-16 hrs/month | $9,600-19,200 |
| Incident response and on-call | 4-8 hrs/month | $4,800-9,600 |
| Security patches and CVE monitoring | 4 hrs/month | $4,800 |
| Total annual engineering overhead | 180-360 hrs/year | $23,000-42,000 |
The honest recommendation
Use managed API gateway if:
- +Your monthly gateway spend is below $2,000
- +You do not have dedicated platform engineering capacity
- +You are on a single cloud and want native integrations
- +High availability is critical and you cannot afford downtime incidents
Consider self-hosted if:
- +Monthly managed costs exceed $2,000 and you are on AWS (not Cloudflare)
- +You have an existing Kubernetes platform team
- +You need features not available in managed gateways (custom Lua plugins, etc.)
- +Data sovereignty or compliance prevents using cloud-managed services
Before deciding, model your total cost using the API gateway cost calculator. Add the engineering overhead from the table above to any self-hosted option to get a true apples-to-apples comparison.