Softwr

Backup · head to head

Borg Backup vs Dokku

Borg Backup logo

Borg Backup

Backup

Deduplicating archiver with compression and encryption

From
Free
Rated
-
Full reviewWebsite
Dokku logo

Dokku

Cloud

Single-server platform that accepts a git push and runs Heroku buildpacks on Docker

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Borg Backup linux, macOS and BSD only; Windows is not a supported platform; Dokku one maintainer accounts for nearly all human commit activity and the project records roughly 10,500 US dollars of annual income on Open Collective, which is not enough to fund a maintainer, so continuity rests on one person continuing to volunteer.
  • They diverge on capability: Borg Backup covers Content-defined chunking, Dokku covers Git push deploy.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Borg Backup and Dokku actually diverge.

Attributes where Borg Backup and Dokku differ
AttributeBorg BackupDokku
Pricing modelfreeOpen source, no licence fee
PlatformsLinux, MacLinux, Docker, CLI, Self-hosted
CategoryBackupCloud
Founded2015Unknown

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 Dokku

  • Git push deploy
  • Heroku buildpacks
  • Datastore plugins
  • Automatic certificates
  • Zero downtime deploys
  • Pluggable schedulers

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 Dokku
  • Encrypted backup to a server you do not fully trust, since the server never sees plaintextnot Dokku
  • Browsing previous versions by mounting an archive over FUSEnot Dokku
  • Scripted server backups with no agent or daemon to runnot Dokku

Dokku

  • Running a dozen side projects and client applications on one virtual private server with Heroku style deploymentnot Borg Backup
  • Moving off a managed platform when the monthly bill has grown faster than the traffic hasnot Borg Backup
  • A consultancy that wants buildpack deployments without teaching every client team Kubernetesnot Borg Backup
  • Keeping a legacy Procfile application alive on hardware you control after a managed platform deprecates its stacknot 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

Dokku

  • One maintainer accounts for nearly all human commit activity and the project records roughly 10,500 US dollars of annual income on Open Collective, which is not enough to fund a maintainer, so continuity rests on one person continuing to volunteer.
  • Dokku Pro asks 849 US dollars for a lifetime licence from a project with no disclosed legal entity behind the promise and no published refund terms, while the product is still described as in development at early bird pricing.
  • Dokku is single-server by design, and the k3s scheduler that provides multi-node support is missing log retrieval, process inspection and content-based health checks, with a post-run hook the documentation says does not consistently fire.
  • Supported operating systems are limited to Ubuntu 22.04 or 24.04 and Debian 11 or later, so organisations standardised on Red Hat, Rocky or Alma Linux cannot run it on their approved base image.
  • Backups are separate commands per datastore plugin that you schedule yourself, with no unified snapshot, no point-in-time recovery and no tested restore path, so verifying that a restore works is entirely your responsibility.

Pricing, plan by plan

Borg Backup

Free
  • FreeFree
    • Deduplication
    • Compression
    • Encryption

Dokku

Free
  • DokkuFree
    • MIT licensed, no usage limits
    • Command line and SSH only
    • All datastore and certificate plugins
  • Dokku Pro$849/one-time
    • Lifetime licence with free upgrades and no subscription
    • Covers 1 production and 2 pre-production servers
    • Web dashboard and JSON REST API

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.
Borg Backup review

Choose Dokku if

  • You need git push deploy.
  • You want to start without paying.
  • You work on Linux, Docker, CLI, Self-hosted.
  • You also want heroku buildpacks.
Dokku review

Questions people ask

Is Borg Backup or Dokku better?
Neither clearly leads. Borg Backup starts at Free and Dokku at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Borg Backup or Dokku?
Borg Backup starts at Free and Dokku at Free.
Does Borg Backup or Dokku run on more platforms?
Borg Backup runs on Linux, Mac. Dokku runs on Linux, Docker, CLI, Self-hosted.
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 Dokku is typically brought in for.
What can Borg Backup do that Dokku cannot?
Borg Backup covers Content-defined chunking, Deduplication, Compression, Authenticated encryption. Dokku covers Git push deploy, Heroku buildpacks, Datastore plugins, Automatic certificates.

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.

Source
Dokku: Is Dokku still maintained?

Yes. Version 0.38.27 shipped in August 2026 with roughly six releases in the preceding two months. The caveat is that one maintainer writes nearly all of it.

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.

Source
Dokku: What does Dokku Pro give me over the free edition?

A web dashboard, a JSON REST API, git push over HTTPS, browser log tailing, team management and email support from the maintainers. It costs 849 US dollars once for one production and two pre-production servers.

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.

Source
Dokku: Can Dokku run across multiple servers?

Only through the k3s or Nomad schedulers. The k3s path is missing several commands and health check types, and the older Kubernetes scheduler is deprecated and no longer developed.

Dokku: Will my Heroku application run on it unchanged?

Usually. Dokku runs the same buildpacks and reads a Procfile, so the application layer normally moves across. Add-ons, scaling behaviour and backups are the parts you have to rebuild.

Share

Related pages

More on Borg Backup

More on Dokku

Keep looking

Other head to heads