Backup · head to head
Borg Backup vs Infracost

Borg Backup
Backup
Deduplicating archiver with compression and encryption
- From
- Free
- Rated
- -

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: Borg Backup linux, macOS and BSD only; Windows is not a supported platform; 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.
- They diverge on capability: Borg Backup covers Content-defined chunking, Infracost covers Pull request cost diffs.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Borg Backup and Infracost actually diverge.
| Attribute | Borg Backup | Infracost |
|---|---|---|
| Pricing model | free | Free open source tool, then per month by run volume |
| Platforms | Linux, Mac | Web, macOS, Linux, Windows, Docker |
| Category | Backup | Cloud |
| Founded | 2015 | Unknown |
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 Borg Backup
- Content-defined chunking
- Deduplication
- Compression
- Authenticated encryption
- Pruning
- Mount archives
- SSH
- BorgBase
Only in Infracost
- Pull request cost diffs
- Multi-format parsing
- Apache-2.0 CLI
- FinOps policies
- Automated remediation
- IDE integration
What people use each for
The jobs each tool is most often brought in to do.
Borg Backup
- Deduplicated backups where daily full snapshots would otherwise be expensivenot Infracost
- Encrypted backup to a server you do not fully trust, since the server never sees plaintextnot Infracost
- Browsing previous versions by mounting an archive over FUSEnot Infracost
- Scripted server backups with no agent or daemon to runnot Infracost
Infracost
- Teams that want an expensive infrastructure change questioned at review rather than discovered on an invoicenot Borg Backup
- Platform groups enforcing tagging so cloud spend can be attributed to a team at allnot Borg Backup
- Organisations adopting FinOps practice without buying a full cloud management platformnot Borg Backup
- Engineers who want a cost figure in the editor while writing the Terraformnot Borg Backup
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Borg Backup
- Linux, macOS and BSD only; Windows is not a supported platform
- Command-line only, with no graphical interface in the project itself
- Version 2.0 is still in beta, so production use means staying on the 1.4 line
- Restoring requires the Borg tooling, since archives are a deduplicated chunk store rather than plain files
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.
Pricing, plan by plan
Borg Backup
Free- FreeFree
- Deduplication
- Compression
- Encryption
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
Which should you pick?
Choose Borg Backup if
- You need content-defined chunking.
- You want to start without paying.
- You work on Linux, Mac.
- You also want deduplication.
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.
Questions people ask
- Is Borg Backup or Infracost better?
- Neither clearly leads. Borg Backup 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, Borg Backup or Infracost?
- Borg Backup starts at Free and Infracost at Free.
- Does Borg Backup or Infracost run on more platforms?
- Borg Backup runs on Linux, Mac. Infracost runs on Web, macOS, Linux, Windows, Docker.
- Can I use Borg Backup for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Borg Backup best used for?
- Borg Backup is most often used for deduplicated backups where daily full snapshots would otherwise be expensive, encrypted backup to a server you do not fully trust, since the server never sees plaintext, browsing previous versions by mounting an archive over fuse, scripted server backups with no agent or daemon to run. Of those, deduplicated backups where daily full snapshots would otherwise be expensive and encrypted backup to a server you do not fully trust, since the server never sees plaintext are not what Infracost is typically brought in for.
- What can Borg Backup do that Infracost cannot?
- Borg Backup covers Content-defined chunking, Deduplication, Compression, Authenticated encryption. Infracost covers Pull request cost diffs, Multi-format parsing, Apache-2.0 CLI, FinOps policies.
Answered from the vendors’ own pages
Borg Backup: What is the cost of BorgBackup?
BorgBackup is completely free and open source under the BSD license with no mandatory costs for the core software.
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.
Borg Backup: Are there paid services available for BorgBackup?
Yes, optional third-party services are available: BorgBase for specialized Borg repository hosting, Hetzner Storage Box with Borg support, and rsync.net cloud storage integration.
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.
Borg Backup: How can I support the BorgBackup project?
BorgBackup accepts voluntary contributions through Open Collective, GitHub Sponsors, Liberapay, and PayPal, though donations are optional.
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.
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
More on Borg Backup
Other head to heads
- Borg Backup vs Kopia
- Borg Backup vs rustic
- Borg Backup vs Backupify
- Borg Backup vs Acronis Cyber Protect
- Borg Backup vs Spanning Backup
- Borg Backup vs CloudAlly
- Borg Backup vs Restic
- Borg Backup vs Clonezilla
- Borg Backup vs Velero
- Borg Backup vs Proxmox Backup Server
- Borg Backup vs Duplicacy
- Borg Backup vs HPE StoreOnce
- Borg Backup vs UrBackup
- Borg Backup vs Windows Backup
- Borg Backup vs Bacula
- Borg Backup vs Comet Backup
- Borg Backup vs NAKIVO Backup & Replication
- Borg Backup vs Portworx Backup
- Borg Backup vs Terragrunt
- Borg Backup vs Pulumi
- Borg Backup vs Packer
- Borg Backup vs Serverless Framework
- Borg Backup vs SST
- Borg Backup vs Coolify
- Borg Backup vs CapRover
- Borg Backup vs DeepInfra
- Borg Backup vs Linode
- Borg Backup vs VictoriaMetrics
- Borg Backup vs Contabo
- Borg Backup vs Chef
- Borg Backup vs Cilium
- Borg Backup vs Vagrant
- Borg Backup vs containerd
- Infracost vs Kopia
- Infracost vs rustic
- Infracost vs Backupify
- Infracost vs Acronis Cyber Protect
- Infracost vs Spanning Backup
- Infracost vs CloudAlly
- Infracost vs Restic
- Infracost vs Clonezilla
- Infracost vs Velero
- Infracost vs Proxmox Backup Server
- Infracost vs Duplicacy
- Infracost vs HPE StoreOnce
- Infracost vs UrBackup
- Infracost vs Windows Backup
- Infracost vs Bacula
- Infracost vs Comet Backup
- Infracost vs NAKIVO Backup & Replication
- Infracost vs Portworx Backup
- 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
