Cloud · head to head
Infracost vs Valkey

Infracost
Cloud
Cloud cost estimates in pull requests, with governance in the paid tier
- 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.; Valkey younger project, so its track record is short even though the codebase is not
- They diverge on capability: Infracost covers Pull request cost diffs, Valkey covers Redis-compatible.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Infracost and Valkey actually diverge.
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 Valkey
- Redis-compatible
- BSD licensed
- Rich data structures
- Replication and persistence
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 Valkey
- Platform groups enforcing tagging so cloud spend can be attributed to a team at allnot Valkey
- Organisations adopting FinOps practice without buying a full cloud management platformnot Valkey
- Engineers who want a cost figure in the editor while writing the Terraformnot Valkey
Valkey
- Continuing on a permissively licensed in-memory store after the Redis licence changenot Infracost
- Caching and session storage where a foundation-governed project is a procurement requirementnot Infracost
- Migrating from Redis without rewriting application codenot 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.
Valkey
- Younger project, so its track record is short even though the codebase is not
- Divergence from Redis grows over time, so compatibility is strongest near the fork point and weakens as both evolve
- Ecosystem tooling and documentation still frequently assume Redis, leaving translation work
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
Valkey
Free- ValkeyFree
- Full functionality
- Self-hosted
- No usage limits
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 Valkey if
- You need redis-compatible.
- You want to start without paying.
- You work on Linux, macOS, Docker, Self-hosted.
- You also want bsd licensed.
Questions people ask
- Is Infracost or Valkey better?
- Neither clearly leads. Infracost starts at Free and Valkey at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Infracost or Valkey?
- Infracost starts at Free and Valkey at Free.
- Does Infracost or Valkey run on more platforms?
- Infracost runs on Web, macOS, Linux, Windows, Docker. Valkey runs on Linux, macOS, Docker, Self-hosted.
- 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 Valkey is typically brought in for.
- What can Infracost do that Valkey cannot?
- Infracost covers Pull request cost diffs, Multi-format parsing, Apache-2.0 CLI, FinOps policies. Valkey covers Redis-compatible, BSD licensed, Rich data structures, Replication and persistence.
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.
Valkey: Is Valkey free?
Yes, BSD-licensed open source under the Linux Foundation.
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.
Valkey: Why does Valkey exist?
Redis changed its licence away from BSD in 2024. Valkey is the community fork continuing under permissive terms, backed by AWS, Google Cloud and Oracle among others.
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.
Valkey: Can I switch from Redis to Valkey?
At the fork point it is drop-in compatible with existing clients and data. The further both projects move from that point, the more you should verify the specific features you use.
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
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 Dragonfly
- Infracost vs Memcached
- Infracost vs MariaDB
- Infracost vs Aiven
- Infracost vs Redpanda
- Infracost vs Timeplus
- Infracost vs PostgreSQL
- Infracost vs Apache Kafka
- Infracost vs RabbitMQ
- Infracost vs Meilisearch
- Infracost vs NATS
- Infracost vs DataGrip
- Infracost vs Estuary
- Infracost vs Apache Airflow
- Infracost vs Apache Pinot
- Infracost vs Apache Pulsar
- Infracost vs Cassandra
- Infracost vs CouchDB
- Valkey vs Terragrunt
- Valkey vs Pulumi
- Valkey vs Packer
- Valkey vs Serverless Framework
- Valkey vs SST
- Valkey vs Coolify
- Valkey vs CapRover
- Valkey vs DeepInfra
- Valkey vs Linode
- Valkey vs VictoriaMetrics
- Valkey vs Contabo
- Valkey vs Chef
- Valkey vs Cilium
- Valkey vs Vagrant
- Valkey vs containerd
- Valkey vs Dragonfly
- Valkey vs Memcached
- Valkey vs MariaDB
- Valkey vs Aiven
- Valkey vs Redpanda
- Valkey vs Timeplus
- Valkey vs PostgreSQL
- Valkey vs Apache Kafka
- Valkey vs RabbitMQ
- Valkey vs Meilisearch
- Valkey vs NATS
- Valkey vs DataGrip
- Valkey vs Estuary
- Valkey vs Apache Airflow
- Valkey vs Apache Pinot
- Valkey vs Apache Pulsar
- Valkey vs Cassandra
- Valkey vs CouchDB

