Softwr

Cloud · head to head

Infracost vs Timeplus

Infracost logo

Infracost

Cloud

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

From
Free
Rated
-
Full reviewWebsite
Timeplus logo

Timeplus

Databases

Streaming SQL engine built on ClickHouse internals, shipping as one small binary

From
Free
Rated
-
Full reviewWebsite

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.; Timeplus proton, the free version, is single-node by design, so any requirement for high availability or horizontal scale forces the commercial licence; the open source edition is a trial in practical terms.
  • They diverge on capability: Infracost covers Pull request cost diffs, Timeplus covers Streaming SQL.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Infracost and Timeplus actually diverge.

Attributes where Infracost and Timeplus differ
AttributeInfracostTimeplus
Pricing modelFree open source tool, then per month by run volumePer month for cloud, quoted for self-hosted
PlatformsWeb, macOS, Linux, Windows, DockerLinux, macOS, Docker, Kubernetes, Web
CategoryCloudDatabases

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 Timeplus

  • Streaming SQL
  • Unified streaming and historical
  • ClickHouse-based engine
  • Single binary deployment
  • External streams
  • Materialised views

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

Timeplus

  • Real-time alerting on Kafka topics where standing up a Flink cluster is more work than the use case justifiesnot Infracost
  • Fraud or anomaly detection that must join a live event stream against recent history in one querynot Infracost
  • Streaming ETL from Kafka or MySQL change data capture into ClickHouse without writing Javanot Infracost
  • A small data team that needs continuous aggregation but has no platform engineers to operate JVM infrastructurenot 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.

Timeplus

  • Proton, the free version, is single-node by design, so any requirement for high availability or horizontal scale forces the commercial licence; the open source edition is a trial in practical terms.
  • It is a young project against Apache Flink’s decade of production history, so the hiring pool, the connector library and the body of known failure modes are all much smaller.
  • Inheriting ClickHouse internals also inherits ClickHouse constraints: memory-hungry queries, awkward updates and a SQL dialect that is not portable to other engines.
  • Exactly-once semantics and state recovery guarantees are less battle-tested than Flink checkpointing, which matters if the pipeline moves money.
  • Cloud pricing is by provisioned instance size rather than usage, so a bursty workload pays for peak capacity around the clock or has to be resized by hand.

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

Timeplus

Free
  • Timeplus ProtonFree
    • Apache 2.0 licence
    • Single node only
    • Full streaming SQL engine
  • Timeplus Cloud$199/month
    • One to thirty-two CPUs
    • 4 GB to 128 GB memory
    • From 250 GB SSD storage
  • Self-hosted or BYOC$undefined/year
    • Multi-node clustering
    • Kubernetes or bare metal
    • Customisable compute and storage

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.
Infracost review

Choose Timeplus if

  • You need streaming sql.
  • You want to start without paying.
  • You work on Linux, macOS, Docker, Kubernetes, Web.
  • You also want unified streaming and historical.
Timeplus review

Questions people ask

Is Infracost or Timeplus better?
Neither clearly leads. Infracost starts at Free and Timeplus at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Infracost or Timeplus?
Infracost starts at Free and Timeplus at Free.
Does Infracost or Timeplus run on more platforms?
Infracost runs on Web, macOS, Linux, Windows, Docker. Timeplus runs on Linux, macOS, Docker, Kubernetes, Web.
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 Timeplus is typically brought in for.
What can Infracost do that Timeplus cannot?
Infracost covers Pull request cost diffs, Multi-format parsing, Apache-2.0 CLI, FinOps policies. Timeplus covers Streaming SQL, Unified streaming and historical, ClickHouse-based engine, Single binary deployment.

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.

Timeplus: Is Timeplus open source?

The core engine, Timeplus Proton, is Apache 2.0. Timeplus Enterprise and Cloud are commercial.

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.

Timeplus: What is the difference from Flink?

Timeplus is one binary with SQL as the only interface; Flink is a JVM cluster with a Java and SQL API and far more operational surface.

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.

Timeplus: Can Proton run in production?

It can, but it is single-node only, so there is no high availability without the commercial edition.

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.

Timeplus: How much is the cloud?

From 199 US dollars a month, sized by CPU and memory, with a fourteen day trial.

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.

Share

Related pages

More on Infracost

More on Timeplus

Keep looking

Other head to heads