| Sizing servers on one cloud | The cloud’s own calculator: AWS, Google Cloud or Oracle. They are free, they need no account, and nothing third-party is more accurate about a vendor than the vendor. |
|---|---|
| Costing a Terraform change before it merges | Infracost. It reads the plan in a pull request and prices the diff, which is the only one of these that answers a question at review time. |
| Finding out where money already went | Holori, Binadox or Flexera One. These are FinOps platforms: they connect to spend that exists and attribute it. They cannot price a stack you have not built. |
| Choosing between Supabase and Firebase, or Clerk and Auth0 | None of the seven above prices managed developer services at all. That is the gap StackTab fills, and it is the only claim this page makes for it. |
| Everything at once | No tool here does infrastructure and the managed layer together. Two tools, two numbers, added by hand. |
Competitor descriptions read 2026-08-23 · StackTab’s own figures 27 Sept 2026 · 64 plans checked · 3 drifted
| Tool | What it prices | What the tool costs | What you need first | Prices Supabase, Clerk, Vercel, Stripe? |
|---|---|---|---|---|
| AWS services only, configured service by service | Free | Nothing. No account, no sign-in | No | |
| Google Cloud Pricing Calculator | Google Cloud services only | Free | Nothing | No |
| Oracle Cloud Infrastructure only | Free | Nothing | No | |
| Infracost | Terraform, CloudFormation and CDK, from the diff in a pull request | Free to 1,000 runs a month; $250/mo for 10,000; $1,000/mo above that | Infrastructure as code, and CI you can install into | No |
| Multi-cloud spend, visualised and allocated after the fact | Not published as a rate card | A connected cloud account with spend in it | No | |
| Flexera One | IT assets, cloud spend and software licences across a hybrid estate | Not published as a rate card | An enterprise estate to connect, and a procurement cycle | Licences, not developer services |
| Binadox | Cloud and SaaS spend already being incurred | 14-day free trial; rate card not published | Connected cloud and SaaS accounts | Spend you already have, not spend you are choosing |
| StackTab | Managed developer services: database, auth, payments, hosting | Free | Nothing. No account, no repository, no cloud connection | Yes: that is the only thing it prices |
Not published as a rate card means the company does not put a price on a public page, not that the tool is expensive or that there is no price. Holori, Flexera and Binadox all route pricing through a demo or a trial. Where a figure is missing here it is missing on their side, and it is recorded as unknown rather than guessed: the same rule this site applies to the 64 vendor plans it prices.
A cloud cost calculator prices a stack you have not built yet; a FinOps platform attributes spend you have already incurred. The AWS Pricing Calculator, the Google Cloud Pricing Calculator and the Oracle Cost Estimator are all in the first group: they are free, they open without an account, and they exist to turn a proposed configuration into a monthly figure. Holori describes itself as “a modern FinOps platform designed to help companies visualize, allocate and optimize cloud costs”, and Binadox as “a unified cloud and SaaS cost management platform offering real-time visibility, automated optimization, and multi-cloud insights”: both read from their own home pages on 23 August 2026. Those are the second group. They need a connected account with real spend in it before they can say anything at all, which makes them useless for the decision most people mean when they search for a cloud cost calculator: choosing, before committing.
Infracost publishes four tiers on its pricing page, read on 23 August 2026: a free CI/CD plan with 1,000 runs a month, Starter at $250 a month for 10,000 runs, Cloud at $1,000 a month, and Enterprise priced on contact. The free plan covers cost estimation for Terraform, CloudFormation and CDK and integrates with GitHub, GitLab and Azure DevOps. Infracost is the only tool on this page that answers a cost question at code review time rather than at planning time or after the invoice, which is a genuinely different job from anything else listed here. Its limit is the same as its premise: it prices infrastructure as code. A Supabase Pro subscription, a Clerk seat charge or a Stripe fee never appears in a Terraform plan, so no amount of Infracost coverage will produce them.
None of the seven infrastructure and FinOps tools above prices managed developer services, which is why StackTab exists. The AWS, Google Cloud and Oracle calculators each price exactly one cloud’s own products. Infracost prices what a Terraform plan declares. Holori, Flexera One and Binadox read spend out of connected accounts, so a service you are still choosing between has no row anywhere. Meanwhile the bill for a small web application is increasingly not infrastructure at all: it is a database subscription, an auth service charging per monthly active user, a payment provider taking a percentage, and a host billing for functions and egress. StackTab prices those four layers together at 1,000, 10,000 and 100,000 users, with every rate read off the vendor’s own public pricing page and re-checked nightly. The last run checked 64 plans and found 3 drifted.
A vendor calculator prices the configuration you describe, and the invoice prices the usage you had. The gap between them is almost always an assumption nobody wrote down: how much egress a given number of users generates, how long a function runs, how much of the database is hot. Google’s calculator says as much in its own description: it builds a quote “based on number, usage, and power of servers”, all three of which are inputs you supply. This is not a flaw in the tool; it is the boundary between a rate, which is a fact the vendor publishes, and a volume, which is a guess about your product. Any cost tool that hides its usage assumptions is not more accurate, only more confident. StackTab prints the assumption beside every figure it produces and lets you change it.
Use the cloud vendors’ own calculators whenever the question involves instances, block storage, data transfer or managed databases you run yourself: StackTab does not price any of that and will not pretend to. Use Infracost if your infrastructure lives in Terraform and you want the cost of a change visible in the pull request that makes it. Use Flexera One if the estate is large enough to have software licences and hybrid IT in scope, which its own description names before it names cloud. Use Holori or Binadox once spend already exists and the question has become where it went rather than what to pick. StackTab is the right tool for exactly one question: what the managed services under a small web application cost together, before you commit to any of them, and for that question none of the other seven has a row to show you.
Every description and figure above was read off the page linked below on 2026-08-23. Nothing here is quoted from a review site, an aggregator or a press release: the same rule the method behind the priced catalogue applies to the vendors it tracks.
AWS Pricing Calculator: calculator.aws, read 2026-08-23- Google Cloud Pricing Calculator: cloud.google.com/products/calculator, read 2026-08-23
Oracle Cost Estimator: oracle.com/cloud/costestimator.html, read 2026-08-23- Infracost: infracost.io/pricing, read 2026-08-23
Holori: holori.com, read 2026-08-23- Flexera One: flexera.com/products/flexera-one, read 2026-08-23
- Binadox: binadox.com, read 2026-08-23