Mr.PlanB Logo
    Open-Source Backup Ledger 2026
    Ledger
    Open-Source Backup Ledger 2026

    BackupPC: Open-Source Backup Ledger 2026

    BackupPC still does what it always did: agentless file backup of many machines into a deduplicated pool with a web console.

    Edition October 2, 20266 min read

    Where BackupPC put its effort, 2017 to 2026

    Each square is one capability area in one year. The brighter it is, the more the area gained in the Open-Source Backup Ledger that year; 1, 2 and 3 mark that year's biggest pushes.

    ’17’18’19’20’21’22’23’24’25’26
    Virtual and physical servers
    Databases and applications
    Recovery
    Cyber resilience
    Storage efficiency and targets
    Long-term retention and tape
    Replication and DR
    Security and compliance
    New-platform support (VMware exit)
    Management at scale and automation
    no change+0.5+1+1.5 or moreScores out of 5 per area.

    No area gained score between 2016 and 2026.

    Part of the Open-Source Backup Ledger (edition 2026-10-02). How the scores work: methodology.

    Snapshot

    • Kind: Backup platform
    • Licence: GPLv3
    • Backer: None; volunteer maintainer since 2025
    • Paid edition or support: None
    • Latest release: 4.4.0 stable (2020-06-20); 4.4.1rc1 (2025-11-13)
    • Next signal: 4.4.1 final; Perl 5.38/5.40 and GCC 14 fixes; no feature work planned
    • Archetype: Revived, low velocity
    • Evidence grade: A. GitHub API and Debian sources.

    Scorecard

    DimensionScoreDirection
    Capability today38.0 / 100higher is better
    Momentum since end of 2022+0.0 pointshigher is better
    Credibility8.5 / 25higher is better
    Sustainability risk17.0 / 25lower is better
    Technical lock-in8.0 / 25lower is better
    Support and ecosystem7.0 / 20higher is better
    AI leverage0.5 / 20higher is better
    Ledger Index33.9 / 100balanced weights

    Capability by domain

    Scores 0 to 5 against fixed anchors; total is weighted to 100.

    Domain (weight)201620192022Today
    Virtual and physical servers (12)2.52.52.52.5
    Databases and applications (12)1111
    Recovery (14)2.52.52.52.5
    Cyber resilience (14)1.51.51.51.5
    Storage efficiency and targets (10)2.52.52.52.5
    Long-term retention and tape (6)3333
    Replication and DR (10)1111
    Security and compliance (8)2222
    New-platform support (VMware exit) (8)1111
    Management at scale and automation (6)2.52.52.52.5
    Total / 10038.038.038.038.0

    Year by year: 2016: 38.0 · 2017: 38.0 · 2018: 38.0 · 2019: 38.0 · 2020: 38.0 · 2021: 38.0 · 2022: 38.0 · 2023: 38.0 · 2024: 38.0 · 2025: 38.0 · 2026: 38.0

    What moved the score

    YearDomainChangePointsTrigger
    n/an/an/an/aNo change since the first scored year

    Direction, 2023 to 2026

    Each item carries one theme and one driver (V vision, C customer need, M market window, U upstream, P portfolio).

    DateItemThemeDriver
    2025-114.4.1rc1: Perl 5.38/5.40 compatibilityD12 Packaging and licensingU
    20264.4.1 final release (pending)D12 Packaging and licensingC
    • Centre of gravity: Packaging and licensing (2)
    • Driver mix: Vision 0%, Customer need 50%, Market window 0%, Upstream 50%, Portfolio 0%

    Credibility: 8.5 / 25

    CriterionScoreBasis
    Cadence1No stable release since June 2020
    Roadmap transparency2.5Public GitHub
    Say-do24 items: 1 shipped, 1 partial, 1 pending, 1 dropped
    Velocity10 commits in 2023, 3 in 2026
    Lifecycle stability2Kept buildable mainly by distribution maintainers

    Say-do record, 2023 to 2026: 4 items: Perl compatibility fixes shipped in 4.4.1rc1; 4.4.1 itself is partial (rc only, 57 months after first proposed); the final release is pending; a modern web UI was dropped.

    Sustainability risk: 17.0 / 25 (lower is better)

    CriterionScoreBasis
    Maintainer concentration4.5One volunteer maintainer
    Backer health4No organisation behind it
    Licence-change risk1GPLv3 with distributed copyright
    Abandonment signs4No stable release in six years; issues median age 1,597 days
    Security response3.5No security process

    Project health: Revived from near-abandonment: zero commits in 2023, new volunteer maintainer (Ged Haywood) published 4.4.1rc1 in November 2025. 1,626 stars; 51 open issues with a median age of 1,597 days.

    Technical lock-in: 8.0 / 25 (lower is better)

    CriterionScoreBasis
    Formats2.5Own content-addressed pool format
    Export path1.5BackupPC_tarCreate extracts files
    Stack coupling1.5Perl daemon with Apache CGI
    Hardware / cloud coupling0Local POSIX filesystem
    Skills and tooling coupling2.5Perl and legacy skills

    Support and ecosystem: 7.0 / 20

    CriterionScoreBasis
    Paid support0.5None
    Consultants and partners1Informal administrators only
    Documentation2.5Manual is complete but dated
    Community and packaging3Packaged in Debian and others; 1.6k stars

    AI leverage: 0.5 / 20

    StrandTodayLatest step
    AI for protection / protecting AI0none
    AI platform stack0none
    AI-assisted operations0none
    Agent openness0.52016: Command line only

    No AI features.

    Reading

    BackupPC still does what it always did: agentless file backup of many machines into a deduplicated pool with a web console. It has had no stable release since 2020, survives on one volunteer, and plans no new features. Fine where it already runs; not a choice for new enterprise deployments.

    Open questions and evidence caveats

    • The 4.4.1 final release is pending; check the maintainer is still active before relying on it.

    Related reading

    More from Open-Source Backup Ledger 2026