Developer Tools · head to head
GitHub Codespaces vs Infracost

GitHub Codespaces
Developer Tools
Cloud hosted development environments configured by dev container files
- From
- Free
- Free plan
- Yes

Infracost
Cloud
Cloud cost estimates in pull requests, with governance in the paid tier
- From
- Free
- Free plan
- Yes
The short version
- Free plans on both; paid from $0.09/mo and $250/mo.
- Only GitHub Codespaces lists dev container based configuration; only Infracost lists multi-format parsing.
- Where GitHub Codespaces falls short: cannot be self hosted, according to GitHub.
- Prices and features on this page were last checked on 20 November 2026.
How do GitHub Codespaces and Infracost differ?
GitHub Codespaces and Infracost differ on pricing model, platforms and category (Developer Tools against Cloud). Only the attributes on which GitHub Codespaces and Infracost actually diverge.
| Attribute | GitHub Codespaces | Infracost |
|---|---|---|
| Pricing model | Usage-based | Free open source tool, then per month by run volume |
| Platforms | Web, Windows, macOS, Linux | Web, macOS, Linux, Windows, Self-hosted |
| Category | Developer Tools | Cloud |
Identical on both: starting price (Free), free tier (Yes).
Not yet recorded: founded for GitHub Codespaces.
Which features does each one have?
They share no listed features; 8 appear only for GitHub Codespaces and 6 only for Infracost. 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 GitHub Codespaces
- Dev container based configuration
- Launch from repository, pull request, commit or template
- Machines from 2 to 32 cores
- Browser based editor
- Connect from Visual Studio Code or IntelliJ
- JetBrains IDEs and JupyterLab support in beta
- Organisation access and spending controls
- Monthly free allowance for personal accounts
Only in Infracost
- Pull request cost diffs
- Multi-format parsing
- Apache-2.0 CLI
- FinOps policies
- Automated remediation
- IDE integration
What is each one used for?
GitHub Codespaces is most often brought in for onboarding contributors without local setup; Infracost for engineers who want a cost figure in the editor while writing the Terraform. The jobs each tool is most often brought in to do.
GitHub Codespaces
- Onboarding contributors without local setupnot Infracost
- Fixing bugs from an open pull requestnot Infracost
- Consistent environments across a teamnot Infracost
- Coding from a tablet or any browsernot Infracost
- Teaching with preconfigured environmentsnot Infracost
Infracost
- Teams that want an expensive infrastructure change questioned at review rather than discovered on an invoicenot GitHub Codespaces
- Platform groups enforcing tagging so cloud spend can be attributed to a team at allnot GitHub Codespaces
- Organisations adopting FinOps practice without buying a full cloud management platformnot GitHub Codespaces
- Engineers who want a cost figure in the editor while writing the Terraformnot GitHub Codespaces
Where do GitHub Codespaces and Infracost fall short?
GitHub Codespaces's most cited limit: cannot be self hosted, according to GitHub. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
GitHub Codespaces
- Cannot be self hosted, according to GitHub
- Requires an internet connection and works with GitHub repositories
- Usage billing grows with machine size, since included compute is weighted by core count
- Organisation use needs admin enablement before developers can create codespaces
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
How much do GitHub Codespaces and Infracost cost?
GitHub Codespaces has a free plan, with paid plans from $0.09/mo; Infracost has a free plan, with paid plans from $250/mo. Plan by plan below, from each vendor's own pricing page.
GitHub Codespaces
Free- Compute$0.09/core hour
- Storage$0.07/gb month
Infracost
Free- FreeFree
- 1,000 runs a month
- Terraform, CloudFormation and CDK estimates
- Community support
- Starter$250/mo
- 10,000 runs a month
- Email support
- Cloud$1,000/mo
- Ten admin seats, developer seats charged separately
- FinOps policies and cost guardrails
- Dashboards and audit trails
- EnterpriseOn request
- SKU-level price overrides for negotiated rates
- Business unit reporting
- SSO with SAML group mapping
Which should you pick?
Choose GitHub Codespaces if
- You need dev container based configuration.
- You want to start without paying.
- You work on Web, Windows, macOS, Linux.
- You also want launch from repository, pull request, commit or template.
Choose Infracost if
- You need pull request cost diffs.
- You want to start without paying.
- You work on Web, macOS, Linux, Windows, Self-hosted.
- You also want multi-format parsing.
Questions people ask
- Is GitHub Codespaces or Infracost better?
- Neither clearly leads. GitHub Codespaces starts at Free and Infracost at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, GitHub Codespaces or Infracost?
- GitHub Codespaces starts at Free and Infracost at Free.
- Does GitHub Codespaces or Infracost run on more platforms?
- GitHub Codespaces runs on Web, Windows, macOS, Linux. Infracost runs on Web, macOS, Linux, Windows, Self-hosted.
- Can I use GitHub Codespaces for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is GitHub Codespaces best used for?
- GitHub Codespaces is most often used for onboarding contributors without local setup, fixing bugs from an open pull request, consistent environments across a team, coding from a tablet or any browser. Of those, onboarding contributors without local setup and fixing bugs from an open pull request are not what Infracost is typically brought in for.
- What can GitHub Codespaces do that Infracost cannot?
- GitHub Codespaces covers Dev container based configuration, Launch from repository, pull request, commit or template, Machines from 2 to 32 cores, Browser based editor. Infracost covers Pull request cost diffs, Multi-format parsing, Apache-2.0 CLI, FinOps policies.
Answered from the vendors’ own pages
GitHub Codespaces: How much does GitHub Codespaces cost?
GitHub's billing documentation lists compute at 0.09 dollars per core hour and storage at 0.07 dollars per GB month. A 2 core machine therefore costs 0.18 dollars per hour.
SourceInfracost: 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.
GitHub Codespaces: Is there a free allowance?
Yes. Personal GitHub Free accounts include 120 compute hours and 15 GB month of storage, and GitHub Pro includes 180 compute hours and 20 GB month. Included compute is weighted by core count.
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.
GitHub Codespaces: Which editors can I use?
Codespaces can be used in the browser or connected from Visual Studio Code or IntelliJ. JetBrains IDEs and JupyterLab are listed as beta.
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.
GitHub Codespaces: Can Codespaces be self hosted?
No. GitHub states that Codespaces cannot be self hosted.
SourceInfracost: 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 GitHub Codespaces
Other head to heads
- GitHub Codespaces vs CodeSandbox
- GitHub Codespaces vs StackBlitz
- GitHub Codespaces vs Coder
- GitHub Codespaces vs Namespace
- GitHub Codespaces vs Ona (formerly Gitpod)
- GitHub Codespaces vs Depot
- GitHub Codespaces vs Keycloak
- GitHub Codespaces vs Blacksmith
- GitHub Codespaces vs ConfigCat
- GitHub Codespaces vs WarpBuild
- GitHub Codespaces vs Docker
- GitHub Codespaces vs Kubernetes
- GitHub Codespaces vs Nx Cloud
- GitHub Codespaces vs Pants Build
- GitHub Codespaces vs Ansible
- GitHub Codespaces vs Deno
- GitHub Codespaces vs ESLint
- GitHub Codespaces vs Git
- GitHub Codespaces vs Terragrunt
- GitHub Codespaces vs Pulumi
- GitHub Codespaces vs Serverless Framework
- GitHub Codespaces vs SST
- GitHub Codespaces vs Vagrant
- GitHub Codespaces vs Coolify
- GitHub Codespaces vs CapRover
- GitHub Codespaces vs Paperspace
- GitHub Codespaces vs Confluent Cloud
- GitHub Codespaces vs Linode
- GitHub Codespaces vs DeepInfra
- GitHub Codespaces vs Puppet
- GitHub Codespaces vs Zipkin
- GitHub Codespaces vs Amazon S3
- GitHub Codespaces vs Azure Functions
- GitHub Codespaces vs Buildah
- GitHub Codespaces vs Crossplane
- GitHub Codespaces vs Packer
- Infracost vs CodeSandbox
- Infracost vs StackBlitz
- Infracost vs Coder
- Infracost vs Namespace
- Infracost vs Ona (formerly Gitpod)
- Infracost vs Depot
- Infracost vs Keycloak
- Infracost vs Blacksmith
- Infracost vs ConfigCat
- Infracost vs WarpBuild
- Infracost vs Docker
- Infracost vs Kubernetes
- Infracost vs Nx Cloud
- Infracost vs Pants Build
- Infracost vs Ansible
- Infracost vs Deno
- Infracost vs ESLint
- Infracost vs Git
- Infracost vs Terragrunt
- Infracost vs Pulumi
- Infracost vs Serverless Framework
- Infracost vs SST
- Infracost vs Vagrant
- Infracost vs Coolify
- Infracost vs CapRover
- Infracost vs Paperspace
- Infracost vs Confluent Cloud
- Infracost vs Linode
- Infracost vs DeepInfra
- Infracost vs Puppet
- Infracost vs Zipkin
- Infracost vs Amazon S3
- Infracost vs Azure Functions
- Infracost vs Buildah
- Infracost vs Crossplane
- Infracost vs Packer
