← Back to home
Comparison · DevOps

Barman vs Froxlor

A side-by-side editorial comparison of Barman and Froxlor — release velocity, themes, recent moves, and the top alternatives to consider.

Barman vs Froxlor: at a glance

FeatureBarmanFroxlor
SectorDevOpsDevOps
Velocity score0.05.0
Sparks · 30d00
Top themespostgresql, backup, object-storage, securityhosting-panel, open-source, security-fixes, php
Last editorial update1h ago4h ago
WebsiteVisit →Visit →

What is Barman?

Barman 3.20.1 closes a CVE that let a writable catalog delete unrelated snapshots.

Barman 3.20.1 fixes CVE-2026-93853: Barman trusted snapshot IDs from the backup catalog, so anyone able to overwrite backup.info could make it delete unrelated cloud snapshots with Barman's own credentials. It now checks snapshot names against provider metadata before deleting. 3.20.0 in August raised the Python floor to 3.12 and added SSE-C encryption, parallel GCS uploads and S3 Outposts support.

Read the full Barman trajectory →

What is Froxlor?

Froxlor's bugfix releases now describe their changes, and most are security fixes.

Froxlor is an open-source server administration panel. After two bugfix tags with nothing but a compare link, 2.3.14 to 2.3.16 carry real notes: 2.3.14 has four security fixes (theme allowlisting, control characters in FTP members, permission checks on MySQL server and cron reads, admin-scoped mail templates), 2.3.15 fixes database, nginx and SSH-key issues, and 2.3.16 adds PHP 8.5 compatibility and honours a hidden-traffic setting in the API.

Read the full Froxlor trajectory →

Barman vs Froxlor: editorial side-by-side

B
Barman
DEVOPS
0.0

Barman 3.20.1 closes a CVE that let a writable catalog delete unrelated snapshots.

◆ Current state

Barman 3.20.1 fixes CVE-2026-93853: Barman trusted snapshot IDs from the backup catalog, so anyone able to overwrite backup.info could make it delete unrelated cloud snapshots with Barman's own credentials. It now checks snapshot names against provider metadata before deleting. 3.20.0 in August raised the Python floor to 3.12 and added SSE-C encryption, parallel GCS uploads and S3 Outposts support.

◆ Where it's heading

After closing the cloud backup-and-restore loop in 3.18 and 3.19, Barman is hardening it for regulated, least-privilege setups: customer-supplied keys, data kept on Outposts, and now a fix aimed exactly at deployments where the uploading identity has fewer rights than Barman. Releases come roughly every two to three months.

◆ Prediction

A 3.21.0 feature release is the likely next step on the usual cadence, probably continuing cloud storage and retention safety work.

F
Froxlor
DEVOPS
5.0

Froxlor's bugfix releases now describe their changes, and most are security fixes.

◆ Current state

Froxlor is an open-source server administration panel. After two bugfix tags with nothing but a compare link, 2.3.14 to 2.3.16 carry real notes: 2.3.14 has four security fixes (theme allowlisting, control characters in FTP members, permission checks on MySQL server and cron reads, admin-scoped mail templates), 2.3.15 fixes database, nginx and SSH-key issues, and 2.3.16 adds PHP 8.5 compatibility and honours a hidden-traffic setting in the API.

◆ Where it's heading

Security fixes now arrive in the regular bugfix releases rather than only in separate security releases, and the notes have returned. The issues are mostly authorization scoping inside the admin and customer API, the same class as the 2.3.11 2FA bypass. PHP 8.5 support keeps the panel installable on current distributions.

◆ Prediction

Expect further 2.3.x releases with authorization fixes in the API, given the four in 2.3.14 and another in 2.3.16.

Alternatives to Barman and Froxlor

Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Barman or Froxlor.

See all Barman alternatives → · See all Froxlor alternatives →

Recent activity from Barman and Froxlor

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 13d agoFroxlorfroxlor bugfix release 2.3.16
  2. 29d agoFroxlorfroxlor bugfix release 2.3.15
  3. 1mo agoBarmanCVE fix: forged catalog could delete unrelated cloud snapshots
  4. 1mo agoFroxlorfroxlor bugfix release 2.3.14
  5. 2mo agoFroxlorfroxlor bugfix release 2.3.13
  6. 2mo agoBarmanPython 3.12 floor, SSE-C keys and AWS Outposts support
  7. 2mo agoFroxlorFroxlor bugfix release 2.3.12
  8. 2mo agoFroxlor2FA bypass, DKIM key exposure and acme.sh argument injection all fixed
  9. 5mo agoBarmanFix cloud-wal-restore missing prefix-colliding WAL files
  10. 5mo agoBarmanCloud restore closes Barman's object-storage lifecycle ⚡
  11. 7mo agoBarmanBlock-level incremental backups land in cloud storage ⚡
  12. 9mo agoBarmanQuery and restore now work on inactive servers

Frequently asked questions

What is the difference between Barman and Froxlor?

They serve adjacent needs but don't currently overlap on shipped themes. Froxlor is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Barman better than Froxlor?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Froxlor is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.

What are the best alternatives to Barman?

Top Barman alternatives in DevOps are ranked by recent ship velocity. Browse the "Barman alternatives" section above for the current picks, or visit /alternatives/barman for the full list with editorial commentary on each.

What are the best alternatives to Froxlor?

Top Froxlor alternatives in DevOps are ranked by recent ship velocity. Browse the "Froxlor alternatives" section above for the current picks, or visit /alternatives/froxlor for the full list with editorial commentary on each.