Cloud · head to head
Infracost vs Spring Cloud Gateway

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

Spring Cloud Gateway
APIs
API gateway built on Project Reactor for building microservices
- 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.; Spring Cloud Gateway released under the Apache 2.0 license, free and open source with no commercial tier
- They diverge on capability: Infracost covers Pull request cost diffs, Spring Cloud Gateway covers Routing.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Infracost and Spring Cloud Gateway actually diverge.
| Attribute | Infracost | Spring Cloud Gateway |
|---|---|---|
| Pricing model | Free open source tool, then per month by run volume | open-source |
| Platforms | Web, macOS, Linux, Windows, Docker | Java, Spring Boot |
| Category | Cloud | APIs |
| Founded | Unknown | 1998 |
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 Spring Cloud Gateway
- Routing
- Path Rewriting
- Circuit Breaker
- Spring Boot
- Spring Security
- Spring Cloud
- Java support
- Spring Boot support
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 Spring Cloud Gateway
- Platform groups enforcing tagging so cloud spend can be attributed to a team at allnot Spring Cloud Gateway
- Organisations adopting FinOps practice without buying a full cloud management platformnot Spring Cloud Gateway
- Engineers who want a cost figure in the editor while writing the Terraformnot Spring Cloud Gateway
Spring Cloud Gateway
- API Developmentnot Infracost
- API Gatewaynot Infracost
- API Testingnot Infracost
- API Documentationnot Infracost
- Microservicesnot 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.
Spring Cloud Gateway
- Released under the Apache 2.0 license, free and open source with no commercial tier
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
Spring Cloud Gateway
Free- Open SourceFree
- Core Spring Cloud Gateway
- Community support
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 Spring Cloud Gateway if
- You need routing.
- You want to start without paying.
- You work on Java, Spring Boot.
- You also want path rewriting.
Questions people ask
- Is Infracost or Spring Cloud Gateway better?
- Neither clearly leads. Infracost starts at Free and Spring Cloud Gateway at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Infracost or Spring Cloud Gateway?
- Infracost starts at Free and Spring Cloud Gateway at Free.
- Does Infracost or Spring Cloud Gateway run on more platforms?
- Infracost runs on Web, macOS, Linux, Windows, Docker. Spring Cloud Gateway runs on Java, Spring Boot.
- 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 Spring Cloud Gateway is typically brought in for.
- What can Infracost do that Spring Cloud Gateway cannot?
- Infracost covers Pull request cost diffs, Multi-format parsing, Apache-2.0 CLI, FinOps policies. Spring Cloud Gateway covers Routing, Path Rewriting, Circuit Breaker, Spring Boot.
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.
Spring Cloud Gateway: Is Spring Cloud Gateway free?
Yes, Spring Cloud Gateway is free and open-source software. It is part of the Spring ecosystem and available through GitHub repositories with open-source dependencies like spring-cloud-starter-gateway-server-webflux and spring-cloud-starter-gateway-server-webmvc.
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.
Spring Cloud Gateway: What enterprise support is available for Spring Cloud Gateway?
Tanzu Spring provides optional enterprise support including Day 0 access to security patches for organizations requiring guaranteed support, but specific pricing is not published on the Spring Cloud Gateway project page.
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.
Infracost: 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 Spring Cloud 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 Appwrite
- Infracost vs Hasura
- Infracost vs PocketBase
- Infracost vs Sanity
- Infracost vs Kong Gateway
- Infracost vs Tyk
- Infracost vs Janus Gateway
- Infracost vs Convoy
- Infracost vs WSO2 API Manager
- Infracost vs Gravitee
- Infracost vs KeystoneJS
- Infracost vs Strapi
- Infracost vs Swagger/OpenAPI
- Infracost vs Thredd
- Infracost vs Thunder Client
- Infracost vs Toqio
- Infracost vs Kong
- Spring Cloud Gateway vs Terragrunt
- Spring Cloud Gateway vs Pulumi
- Spring Cloud Gateway vs Packer
- Spring Cloud Gateway vs Serverless Framework
- Spring Cloud Gateway vs SST
- Spring Cloud Gateway vs Coolify
- Spring Cloud Gateway vs CapRover
- Spring Cloud Gateway vs DeepInfra
- Spring Cloud Gateway vs Linode
- Spring Cloud Gateway vs VictoriaMetrics
- Spring Cloud Gateway vs Contabo
- Spring Cloud Gateway vs Chef
- Spring Cloud Gateway vs Cilium
- Spring Cloud Gateway vs Vagrant
- Spring Cloud Gateway vs containerd
- Spring Cloud Gateway vs Appwrite
- Spring Cloud Gateway vs Hasura
- Spring Cloud Gateway vs PocketBase
- Spring Cloud Gateway vs Sanity
- Spring Cloud Gateway vs Kong Gateway
- Spring Cloud Gateway vs Tyk
- Spring Cloud Gateway vs Janus Gateway
- Spring Cloud Gateway vs Convoy
- Spring Cloud Gateway vs WSO2 API Manager
- Spring Cloud Gateway vs Gravitee
- Spring Cloud Gateway vs KeystoneJS
- Spring Cloud Gateway vs Strapi
- Spring Cloud Gateway vs Swagger/OpenAPI
- Spring Cloud Gateway vs Thredd
- Spring Cloud Gateway vs Thunder Client
- Spring Cloud Gateway vs Toqio
- Spring Cloud Gateway vs Kong
