Softwr

Cloud · head to head

Infracost vs Upstash

Infracost logo

Infracost

Cloud

Cloud cost estimates in pull requests, with governance in the paid tier

From
Free
Rated
-
Upstash logo

Upstash

Cloud

Serverless data for modern developers

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.; Upstash hTTP-based REST API only, no TCP connections means higher latency than self-hosted or connection-pooled Redis
  • They diverge on capability: Infracost covers Pull request cost diffs, Upstash covers Serverless Redis.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Infracost and Upstash actually diverge.

Attributes where Infracost and Upstash differ
AttributeInfracostUpstash
Pricing modelFree open source tool, then per month by run volumeUnknown
PlatformsWeb, macOS, Linux, Windows, DockerREST API, Node.js, Python, Go, Rust, Vercel Edge, Cloudflare Workers, AWS Lambda
FoundedUnknown2020

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Cloud).

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 Upstash

  • Serverless Redis
  • Serverless Kafka
  • QStash
  • Global Replication
  • REST API
  • Edge Functions Support
  • Rate Limiting
  • Caching

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 Upstash
  • Platform groups enforcing tagging so cloud spend can be attributed to a team at allnot Upstash
  • Organisations adopting FinOps practice without buying a full cloud management platformnot Upstash
  • Engineers who want a cost figure in the editor while writing the Terraformnot Upstash

Upstash

  • Cachingnot Infracost
  • Session storagenot Infracost
  • Real-time messagingnot Infracost
  • Rate limitingnot Infracost
  • Serverless backendsnot 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.

Upstash

  • HTTP-based REST API only, no TCP connections means higher latency than self-hosted or connection-pooled Redis
  • Rate limiting occurs when traffic exceeds configured budget cap or request limits
  • Kafka service discontinued in March 2025, requiring migration to Upstash Workflow or alternatives
  • Limited Redis feature support compared to self-hosted Redis or Redis Cloud
  • High-request-volume workloads can accumulate significant costs due to per-request pricing model

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

Upstash

Free
  • FreeFree
    • 256 MB data
    • 500K commands per month
    • 10 GB bandwidth
  • Pay-as-you-go$0.2/per 100K commands
    • Per-request billing
    • Storage at $0.25/GB
    • Unlimited commands
  • Fixed Plan$10/month
    • 250 MB Redis
    • Predictable pricing
    • Global replication available at higher tiers

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 Upstash if

  • You need serverless redis.
  • You want to start without paying.
  • You work on REST API, Node.js, Python, Go, Rust, Vercel Edge, Cloudflare Workers, AWS Lambda.
  • You also want serverless kafka.

Questions people ask

Is Infracost or Upstash better?
Neither clearly leads. Infracost starts at Free and Upstash at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Infracost or Upstash?
Infracost starts at Free and Upstash at Free.
Does Infracost or Upstash run on more platforms?
Infracost runs on Web, macOS, Linux, Windows, Docker. Upstash runs on REST API, Node.js, Python, Go, Rust, Vercel Edge, Cloudflare Workers, AWS Lambda.
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 Upstash is typically brought in for.
What can Infracost do that Upstash cannot?
Infracost covers Pull request cost diffs, Multi-format parsing, Apache-2.0 CLI, FinOps policies. Upstash covers Serverless Redis, Serverless Kafka, QStash, Global Replication.

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.

Upstash: Does Upstash have a free tier?

Yes. The free tier provides 256 MB of data and 500,000 commands per month with 10 GB of bandwidth in a single region, no credit card required.

Source
Infracost: 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.

Upstash: How does Upstash work with edge platforms like Vercel and Cloudflare Workers?

Upstash uses a REST API instead of TCP connections, enabling it to work from Vercel Edge, Cloudflare Workers, and AWS Lambda without persistent connections or connection pooling.

Source
Infracost: 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.

Upstash: What programming languages are supported?

Upstash provides native SDKs for Python, Node.js, Go, and Rust. Java, C#, and PHP developers can use the REST API or community libraries.

Source
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.

Upstash: Is Upstash Kafka still available?

No. Upstash Kafka was deprecated on September 11, 2024 and fully discontinued on March 11, 2025. Upstash Workflow is now recommended for durable serverless messaging and task queuing.

Source
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.

Upstash: How is Upstash pricing structured?

Upstash uses per-request pricing at $0.20 per 100K commands for Redis, $0.25/GB for storage, and $0.40 per 100K requests for Vector database. Idle applications cost nothing.

Source
Upstash: Can Upstash be used with AWS Lambda?

Yes. Upstash works with AWS Lambda via its REST API, eliminating the need for connection pooling and making it ideal for stateless serverless functions.

Source
Share

Related pages

Other head to heads