Mr.PlanB Logo
    Enterprise Linux Ledger 2026
    Ledger
    Enterprise Linux Ledger 2026

    openSUSE Leap: Enterprise Linux Ledger 2026 Scorecard

    Leap gives you the SLES 16 base for free with 24 months per minor; its lifecycle text conflicts and its future rests on one sponsor.

    Edition October 16, 20267 min read

    Where Leap put its effort, 2016 to 2026

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

    ’16’17’18’19’20’21’22’23’24’25’26
    Lifecycle and upgrades
    Security and compliance1
    Hardware and architectures
    Virtualization and cloud images
    Containers and Kubernetes host2
    Software currency and packaging
    Fleet management and automation3
    Storage and filesystems
    Enterprise integration and certifications
    AI and GPU readiness1
    no change+0.5+1+1.5 or moreScores out of 5 per area.

    Biggest pushes overall: Security and compliance (+1), Containers and Kubernetes host (+1), Fleet management and automation (+1). Already strong in 2015: Storage and filesystems, Hardware and architectures, Virtualization and cloud images.

    Top focus each year: 2018 AI and GPU readiness; 2025 Security and compliance. 9 of 11 years show no gain in any area.

    Part of the Enterprise Linux Ledger (edition 2026-10-16). How the scores work: methodology.

    Snapshot

    • Type: community project
    • Owner: openSUSE Project, sponsored by SUSE (elected openSUSE Board)
    • Licence: Free and open source; no subscription; a migration tool moves a system to SLES for paid support
    • Latest release: 16.0 (2025-10-01); 16.1 at release candidate (2026-09-28)
    • Support lifecycle: Each 16.x minor gets 24 months of community support across two minors; 16.0 is listed to 2027-10-31 on endoflife.date; the 16 family is planned to 16.6 in autumn 2031
    • Next milestone: 16.1 general availability planned for November 2026, the same day as SLES 16.1
    • Support window: 24 months per minor (community); the family runs to 2031 and beyond; no paid extension other than migrating to SLES; source: Leap 16.0 release notes
    • Tier: Community distribution
    • Archetype: Community twin of SLES
    • Evidence grade: B. The Leap 16.0 release notes, the 42.1 release announcement, the 16.1 release candidate posts and the Multi-Linux Manager 5.1 release notes were read directly. Release and end dates come from endoflife.date; the openSUSE lifetime wiki returned HTTP 403. The arrival of the Arm and Power ports and of Podman in the 15 line was not re-read.

    Scorecard

    DimensionScoreDirection
    Capability today63.0 / 100higher is better
    Momentum since end of 2022+10.5 points (2015 to 2022: +1.0)higher is better
    Credibility16.5 / 25higher is better
    Sustainability risk9.0 / 25lower is better
    Technical lock-in4.0 / 25lower is better
    Integrator fit6.5 / 20higher is better
    AI leverage2.0 / 20higher is better
    Ledger Index56.9 / 100balanced weights; see the methodology

    Capability by domain, 2015 to today

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

    Domain (weight)201520192022Today
    Lifecycle and upgrades (15)2.52.52.53
    Security and compliance (15)2.52.52.53.5
    Hardware and architectures (10)3.53.53.54
    Virtualization and cloud images (10)3.53.53.53.5
    Containers and Kubernetes host (10)2.52.52.53.5
    Software currency and packaging (10)3333.5
    Fleet management and automation (10)1.51.51.52.5
    Storage and filesystems (5)4.54.54.54.5
    Enterprise integration and certifications (5)2222
    AI and GPU readiness (10)11.51.51.5
    Total / 10051.552.552.563.0

    Year by year: 2015: 51.5 · 2016: 51.5 · 2017: 51.5 · 2018: 52.5 · 2019: 52.5 · 2020: 52.5 · 2021: 52.5 · 2022: 52.5 · 2023: 52.5 · 2024: 52.5 · 2025: 63.0 · 2026: 63.0

    What moved the score

    YearDomainChangePointsTrigger
    2018AI and GPU readiness1 → 1.5+1.015: NVIDIA CUDA repository for openSUSE 15 (start date not read); none listed for Leap 16 as of 2026-10-15
    2025Containers and Kubernetes host2.5 → 3.5+2.016.0: Podman 5.4 in the base; Leap Micro as the container-host sibling; immutable mode follows in 16.1 (release candidate 2026-09)
    2025Fleet management and automation1.5 → 2.5+2.0Uyuni (upstream of SUSE Multi-Linux Manager) manages Leap; Multi-Linux Manager 5.1 lists Leap 16.0 as a client
    2025Hardware and architectures3.5 → 4+1.016.0: x86-64-v2, POWER10, z14 and Armv8.0-A baselines; 32-bit support removed
    2025Lifecycle and upgrades2.5 → 3+1.516.0: a minor every 12 months with 24 months of community support each; family planned to 16.6 in 2031; migration tool from 15.6
    2025Security and compliance2.5 → 3.5+3.016.0: SELinux by default (AppArmor not selectable at install); AMD SEV-SNP for KVM guests; Intel TDX kernel patches
    2025Software currency and packaging3 → 3.5+1.016.0: 12-month minors refresh the stacks (16.1 moves to PHP 8.5, MariaDB 12.3, QEMU 11 and LLVM 21)

    Direction, 2023 to 2026

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

    DateItemThemeDriver
    2023-0615.5 (2023-06-07) on SLE 15 SP5 sourcesLifecycleU
    2023-08Sponsor SUSE taken private by EQTGovernanceP
    2024-0615.6 (2024-06-12), the final Leap 15 minorLifecycleU
    2025-07Multi-Linux Manager 5.1 lists Leap 16.0 as a managed clientFleet managementU
    2025-1016.0 (2025-10-01): SELinux default, AppArmor not selectable at installSecurityU
    2025-1016.0: Agama installer; x86-64-v2, POWER10 and z14 baselines; 32-bit removedHardwareU
    2025-1016.0: AMD SEV-SNP for KVM guests; Intel TDX kernel patchesVirtualization and cloudU
    2025-1016.0: 12-month minors with 24 months of community support; migration tool from 15.6 that also offers SLESLifecycleV
    2026-03EQT sale process for SUSE reportedGovernanceP
    2026-0415.6 end of life (2026-04-30, endoflife.date)LifecycleU
    2026-0916.1 release candidate about a week behind the 2026-09-16 roadmap date; GA synced to SLES 16.1 in NovemberLifecycleU
    2026-0916.1 release candidate: immutable mode with a read-only root replaces Leap MicroContainersV
    2026-0916.1 release candidate: Podman 5.8, QEMU 11, PHP 8.5, MariaDB 12.3, LLVM 21PackagingU
    2026-0916.1 release candidate: appliance images for KVM and Xen, Hyper-V, VMware, Harvester and cloudVirtualization and cloudC
    • Centre of gravity: Lifecycle (5), Governance (2), Virtualization and cloud (2)
    • Blind spots (no items): Storage, Enterprise integration, AI, Licensing
    • Driver mix: Vision 14%, Customer need 7%, Market window 0%, Upstream 64%, Portfolio 14%
    • Idea-to-need index: 0.67 (0 = demand-pulled, 1 = thesis-pushed)

    Credibility: 16.5 / 25

    CriterionScoreBasis
    Cadence3.5Yearly minors (June in the 15 line, November with SLES from 16); the 16.1 release candidate ran a week late against a published roadmap
    Roadmap transparency4Public roadmap with dated milestones, release notes and news posts; the lifetime wiki was not reachable in this pass
    Say-do3.516.0 shipped on the announced day; the 16.1 release candidate slipped about a week; the 2034 support text in the release notes contradicts the 24-month policy
    Velocity2.5Minors are mostly rebases of SLE service packs; 16.0 brought the one big change
    Lifecycle stability324 months per minor means an upgrade every one to two years; 15 to 16 changed the installer, the security module and the CPU baseline

    Sustainability risk: 9.0 / 25 (lower is better)

    CriterionScoreBasis
    Maintainer concentration3Release engineering and most packages come from SUSE staff; community packagers add the rest
    Backer health3One sponsor, SUSE, itself owned by private equity with a sale reported in 2026
    Licence-change risk0.5Open-source packages from SLE and Factory; no single licensor
    Abandonment signs1.5Leap 16 is planned to 16.6 in 2031, but the project depends on SUSE keeping the SLES 16 base open
    Security response1Security updates flow from SUSE's SLE maintenance on the same day

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

    CriterionScoreBasis
    Formats0.5RPM, qcow2 and OCI; Btrfs root readable on any Linux
    Export path1Supported migration to SLES; moving anywhere else is a reinstall
    Stack coupling0.5Uyuni optional; any storage and network
    Hardware / cloud coupling116 requires x86-64-v2 and POWER10; otherwise any server, fully offline
    Skills and tooling coupling1zypper, Agama and SELinux skills; a smaller pool than the Debian and RHEL families

    Integrator fit: 6.5 / 20

    CriterionScoreBasis
    Partner programme openness1None; SUSE partners cover SLES
    Multi-tenancy and self-service0.5None; Uyuni is a separate project
    API and infrastructure-as-code3Salt, Ansible, cloud-init and the Uyuni API
    Skills and certification2SUSE skills transfer; no Leap certification

    AI leverage: 2.0 / 20

    How the product uses AI, scored per year like capability. Only GA counts.

    Criterion20192022TodayLatest step
    AI workload support1.51.51.52018: NVIDIA CUDA repository for openSUSE 15 (start date not read); none listed for 16 as of 2026-10-15
    AI platform stack0002015: None
    AI-assisted operations0002015: None
    Agent openness0.50.50.52015: Uyuni's XML-RPC API is the only agent-drivable surface and belongs to a separate project

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

    AI say-do, 2023 to 2026: 0 AI items announced; 0 GA, 0 still preview, 0 pending, 0 dropped. No AI items were announced for Leap; SUSE's MCP previews ship in SLES 16.

    Leap carries whatever GPU support NVIDIA and AMD publish for it, and NVIDIA's repository list has no Leap 16 entry yet. There is no AI platform, no assistant and no agent interface in the project itself.

    Reading

    Leap is SLES 16 without the subscription, released the same day and patched from the same maintenance stream, which is why its security and storage lines match the commercial product. What it lacks is everything SUSE sells: certifications, live patching, support beyond 24 months per minor and a management product of its own. The lifecycle is the weak point and the published text is contradictory, with release notes that copy the SLES 2034 date next to a 24-month community policy. The thing to check is the upgrade rhythm: plan a minor upgrade every year or two, and treat the migration tool to SLES as the paid exit.

    Open questions and items to re-score

    • Leap 16 lifecycle conflict: the 16.0 release notes say each minor gets 24 months of community support and also that 16.0 is 'fully maintained and supported until 31 Jul 2034' with support to December 2037 (text adapted from SLES 16); endoflife.date lists 16.0 to 2027-10-31; the lifetime wiki returned HTTP 403. The Ledger scores the 24-month policy.
    • Leap 16.1 general availability: planned for November 2026 in step with SLES 16.1; the release candidate ran about a week behind the roadmap.
    • Leap Micro's end date now that 16.1 brings an immutable mode (the release candidate post says it replaces Leap Micro).
    • NVIDIA's CUDA repository index lists opensuse15, sles16 and suse16 but no opensuse16 entry; whether the suse16 repository serves Leap 16 was not confirmed.
    • Arrival dates of the Arm64 and POWER ports and of Podman in the 15 line (grade C); hardware and container values for 2018 to 2024 may be understated by half a step.
    • Kernel live patching availability for Leap (not verified; assumed absent in the community edition).
    • openSUSE Foundation and Board structure (news site categories only).

    Related reading

    More from Enterprise Linux Ledger 2026