Cloud · head to head
Infracost vs Kong Gateway

Infracost
Cloud
Cloud cost estimates in pull requests, with governance in the paid tier
- From
- Free
- Rated
- -

Kong Gateway
APIs
Open-source and cloud API gateway for managing microservices traffic
- From
- Free
- Rated
- -
The short version
- Each has a real cost: Infracost usage-based resources such as object storage, serverless functions and data transfer have no cost without monthly usage figures supplied by hand, and the documentation warns plainly that engineers otherwise read them as free.; Kong Gateway the free open-source gateway lacks the analytics, portals, and support of the paid Konnect tiers.
- They diverge on capability: Infracost covers Pull request cost diffs, Kong Gateway covers API request routing.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Infracost and Kong Gateway actually diverge.
| Attribute | Infracost | Kong Gateway |
|---|---|---|
| Pricing model | Free open source tool, then per month by run volume | freemium |
| Platforms | Web, macOS, Linux, Windows, Docker | web, linux, api |
| Category | Cloud | APIs |
| Founded | Unknown | 2017 |
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Infracost
- Pull request cost diffs
- Multi-format parsing
- Apache-2.0 CLI
- FinOps policies
- Automated remediation
- IDE integration
Only in Kong Gateway
- API request routing
- Plugin ecosystem
- Developer portals
- AI Gateway
- Analytics and observability
- SSO and audit logs
What people use each for
The jobs each tool is most often brought in to do.
Infracost
- Teams that want an expensive infrastructure change questioned at review rather than discovered on an invoicenot Kong Gateway
- Platform groups enforcing tagging so cloud spend can be attributed to a team at allnot Kong Gateway
- Organisations adopting FinOps practice without buying a full cloud management platformnot Kong Gateway
- Engineers who want a cost figure in the editor while writing the Terraformnot Kong Gateway
Kong Gateway
- Routing and securing traffic across microservicesnot Infracost
- Publishing internal or external developer portalsnot Infracost
- Managing rate limits and authentication at the API edgenot Infracost
- Gateway-level routing to multiple LLM providersnot Infracost
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Infracost
- Usage-based resources such as object storage, serverless functions and data transfer have no cost without monthly usage figures supplied by hand, and the documentation warns plainly that engineers otherwise read them as free.
- Splitting production from non-production usage assumptions is not supported in the free usage file, which the docs attribute to a missing project filter, so that separation requires the paid product.
- The step from 250 to 1,000 dollars a month is large and the Cloud tier includes only ten admin seats, with developer seats charged at a figure that is not published, so the cost for a large organisation cannot be computed from the pricing page.
- Estimates are list price. Negotiated agreements, committed use discounts and reserved instance economics require SKU-level overrides available only on Enterprise, so the number in the pull request is not the number on the bill.
- The share of the product covered by the Apache-2.0 licence is shrinking. Checks, automated fixes, policies and agent integrations are all hosted-only, so the permissive licence increasingly protects the estimation engine rather than the product.
Kong Gateway
- The free open-source gateway lacks the analytics, portals, and support of the paid Konnect tiers.
- Plus tier caps API requests at 1M/month before incurring per-million overage charges.
- Enterprise pricing is custom and not published, making budgeting harder without sales contact.
- Configuration and plugin management can require significant operational expertise to run at scale.
Pricing, plan by plan
Infracost
Free- FreeFree
- 1,000 runs a month
- Terraform, CloudFormation and CDK estimates
- Community support
- Starter$250/month
- 10,000 runs a month
- Email support
- Cloud$1000/month
- Ten admin seats, developer seats charged separately
- FinOps policies and cost guardrails
- Dashboards and audit trails
- Enterprise$undefined/year
- SKU-level price overrides for negotiated rates
- Business unit reporting
- SSO with SAML group mapping
Kong Gateway
Free- Free TrialFree
- 30-day enterprise functionality trial
- Unlimited gateways
- 30-day analytics retention
- Plus$undefined/month
- Up to 5 serverless, 2 hybrid, 2 dedicated cloud gateways
- 1M API requests/month included
- Up to 2 developer portals
- Enterprise$undefined/month
- Unlimited hybrid and dedicated cloud gateways
- Unlimited developer portals
- SSO and audit logs
Which should you pick?
Choose Infracost if
- You need pull request cost diffs.
- You want to start without paying.
- You work on Web, macOS, Linux, Windows, Docker.
- You also want multi-format parsing.
Choose Kong Gateway if
- You need api request routing.
- You want to start without paying.
- You work on web, linux, api.
- You also want plugin ecosystem.
Questions people ask
- Is Infracost or Kong Gateway better?
- Neither clearly leads. Infracost starts at Free and Kong Gateway at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Infracost or Kong Gateway?
- Infracost starts at Free and Kong Gateway at Free.
- Does Infracost or Kong Gateway run on more platforms?
- Infracost runs on Web, macOS, Linux, Windows, Docker. Kong Gateway runs on web, linux, api.
- Can I use Infracost for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Infracost best used for?
- Infracost is most often used for teams that want an expensive infrastructure change questioned at review rather than discovered on an invoice, platform groups enforcing tagging so cloud spend can be attributed to a team at all, organisations adopting finops practice without buying a full cloud management platform, engineers who want a cost figure in the editor while writing the terraform. Of those, teams that want an expensive infrastructure change questioned at review rather than discovered on an invoice and platform groups enforcing tagging so cloud spend can be attributed to a team at all are not what Kong Gateway is typically brought in for.
- What can Infracost do that Kong Gateway cannot?
- Infracost covers Pull request cost diffs, Multi-format parsing, Apache-2.0 CLI, FinOps policies. Kong Gateway covers API request routing, Plugin ecosystem, Developer portals, AI Gateway.
Answered from the vendors’ own pages
Infracost: Is the open source version genuinely useful on its own?
Yes, for estimation. It parses your definitions and produces breakdowns and diffs locally. What it does not do is comment on pull requests, enforce policy or report across an organisation, all of which are hosted-only.
Kong Gateway: Is Kong Gateway free?
Kong's core gateway is open source and free to self-host. Kong Konnect, the managed cloud platform, offers a 30-day free trial before moving to paid Plus or custom Enterprise pricing.
SourceInfracost: Will the estimate match my cloud bill?
No. It is list price. Committed use discounts, enterprise agreements and reserved instances need SKU-level overrides that sit in the Enterprise tier.
Kong Gateway: How is usage metered on the Plus plan?
The Plus plan includes 1M API requests per month, with additional usage billed at $200 per extra 1 million requests up to a 10M/month cap, plus per-gateway and per-LLM-model charges.
SourceInfracost: Why do my S3 and Lambda resources show no cost?
Usage-based resources need monthly usage values supplied in a usage file or defined centrally. Without them they estimate at zero, which is the documented behaviour and the most common way the tool misleads.
Kong Gateway: What support is included?
Plus includes email support with a 2-business-day SLA, while Enterprise adds dedicated success managers and professional services.
SourceInfracost: Has the licence ever changed?
No. The command line tool has been Apache 2.0 throughout, with no Business Source or AGPL episode, which is unusual in this category.
Infracost: What is a run?
Not defined on the public pricing page, and the run allowance is what separates the free and Starter tiers, so establish the definition before choosing between them.
Related pages
More on Kong Gateway
Other head to heads
- Infracost vs Terragrunt
- Infracost vs Pulumi
- Infracost vs Packer
- Infracost vs Serverless Framework
- Infracost vs SST
- Infracost vs Coolify
- Infracost vs CapRover
- Infracost vs DeepInfra
- Infracost vs Linode
- Infracost vs VictoriaMetrics
- Infracost vs Contabo
- Infracost vs Chef
- Infracost vs Cilium
- Infracost vs Vagrant
- Infracost vs containerd
- Infracost vs Tyk
- Infracost vs Moesif
- Infracost vs Treblle
- Infracost vs Convoy
- Infracost vs Janus Gateway
- Infracost vs Spring Cloud Gateway
- Infracost vs Gravitee
- Infracost vs Strapi
- Infracost vs WSO2 API Manager
- Infracost vs AWS API Gateway
- Infracost vs GraphQL Apollo
- Infracost vs Appwrite
- Infracost vs Payload CMS
- Infracost vs Portkey
- Infracost vs Prisma
- Infracost vs RapidAPI
- Infracost vs REST Client VSCode
- Infracost vs Rutter
- Kong Gateway vs Terragrunt
- Kong Gateway vs Pulumi
- Kong Gateway vs Packer
- Kong Gateway vs Serverless Framework
- Kong Gateway vs SST
- Kong Gateway vs Coolify
- Kong Gateway vs CapRover
- Kong Gateway vs DeepInfra
- Kong Gateway vs Linode
- Kong Gateway vs VictoriaMetrics
- Kong Gateway vs Contabo
- Kong Gateway vs Chef
- Kong Gateway vs Cilium
- Kong Gateway vs Vagrant
- Kong Gateway vs containerd
- Kong Gateway vs Tyk
- Kong Gateway vs Moesif
- Kong Gateway vs Treblle
- Kong Gateway vs Convoy
- Kong Gateway vs Janus Gateway
- Kong Gateway vs Spring Cloud Gateway
- Kong Gateway vs Gravitee
- Kong Gateway vs Strapi
- Kong Gateway vs WSO2 API Manager
- Kong Gateway vs AWS API Gateway
- Kong Gateway vs GraphQL Apollo
- Kong Gateway vs Appwrite
- Kong Gateway vs Payload CMS
- Kong Gateway vs Portkey
- Kong Gateway vs Prisma
- Kong Gateway vs RapidAPI
- Kong Gateway vs REST Client VSCode
- Kong Gateway vs Rutter
