Mr.PlanB Logo

    #24 of 28 infrastructure automation tools · Updated October 2026

    Salt review 2026

    Salt (Salt Project and VMware Cloud Foundation SaltStack) · Capable core, shrinking under a portfolio owner

    Salt ranks #24 of 28 infrastructure automation tools in the Infrastructure Automation Ledger 2026, with a Ledger Index of 47.5 out of 100. Agent-based engine with real scale and event-driven depth, kept by a small Broadcom team that cut modules from core and slipped its LTS by 19 months.

    Scores

    Ledger Index
    47.5/100
    #24 of 28
    Capability
    60/100
    Credibility
    12.5/25
    Commercial risk
    15.5/25
    lower is better
    Lock-in
    8/25
    lower is better
    AI delivery
    1.5/20

    Source: Infrastructure Automation Ledger 2026, edition 2026-10-16. How each score works: methodology.

    Pros

    • Configuration management depth4.5/5
    • Scale and control plane4.5/5

    Cons

    • AI assistance0/5
    • Provisioning breadth2/5
    • Bare metal and day-2 operations2.5/5

    What the Ledger says

    Salt still does the hard parts well: an agent fleet with an event bus, master clustering, scheduled enforcement and a dry run that works everywhere, which is why its configuration, scale and orchestration scores match or beat Ansible's engine. Everything around that core has contracted since Broadcom took over: modules left core without a deprecation period, the vSphere and Proxmox paths are deprecated or idle, named maintainers have left and the LTS slipped three times. The one thing a buyer should check is the team behind the next release, because the open-source cadence now depends on a handful of Broadcom engineers and the commercial edition has a published end of support in October 2028.

    Salt has no AI code generation, no assistant and no agent interface for operators. The only AI-related code in the project serves its own developers, so the score rests on the REST API alone.

    Capability by area

    Provisioning breadth2/5
    Configuration management depth4.5/5
    State, planning and safety3/5
    Language and authoring3/5
    Orchestration and self-service3.5/5
    Scale and control plane4.5/5
    Security and compliance3.5/5
    Bare metal and day-2 operations2.5/5
    Ecosystem and integrations3/5
    AI assistance0/5

    Buying, lock-in and release record

    Buying and licence (commercial risk)(lower is better)

    Price and licence volatility3
    Engine licence unchanged; the commercial product was repackaged twice since 2023 and standalone sales ended in January 2024
    Purchase constraints3
    Engine is free; the commercial edition is quote only through Broadcom with no published metric
    Channel and access2.5
    Open downloads for the engine; the 3008 compatibility patch for the commercial RaaS plugin is only on the Broadcom support portal
    Owner stability4
    Post-acquisition owner with team cuts, founder and a core maintainer gone, and 19 of the 20 newest commits from one account in September 2026
    Cost of staying supported3
    Forced move from 3006 to 3008 with module removals; commercial support ends October 2028

    Technical lock-in(lower is better)

    Formats1.5
    SLS files are YAML and Jinja in plain text, Salt specific
    Export path3
    No conversion path to another tool; states and pillar need rewriting
    Stack coupling1
    Master and minion over ZeroMQ or TCP with bundled Python; the commercial UI needs the RaaS stack
    Hardware / cloud coupling0.5
    Any host, fully offline
    Skills and tooling coupling2
    Skills common among long-term users and scarcer in the market than Ansible's

    Release credibility

    Cadence3
    Point releases about monthly on the maintained lines; majors irregular, 26 months between 3007.0 and 3008.0
    Roadmap transparency3
    Open Hour posts and the project blog; no written roadmap and no 3009 plan
    Say-do1.5
    3008 LTS was promised for fall 2024, April 2025 and fall 2025 and shipped 2026-05-27
    Velocity2.5
    One or two substantive items per major (clustering in 3007, Resources in 3008), with two years between majors
    Lifecycle stability2.5
    LTS windows are clear, but the STS line ended early, 3006 dropped to security only and 3008 removed modules without a deprecation period

    Partners and services

    Partner programme openness2
    No Salt-specific programme; the commercial edition goes through Broadcom's channel
    Multi-tenancy and self-service2
    External auth ACLs on the master; tenant roles and a UI only in the commercial edition
    API and infrastructure-as-code3.5
    salt-api, runners and the event bus; netapi clients are off by default since 3006.0
    Skills and certification2
    No certification found; shrinking public community

    Alternatives to Salt

    Questions about Salt

    Is Salt any good?

    Salt ranks #24 of 28 infrastructure automation tools in the Infrastructure Automation Ledger 2026, with a Ledger Index of 47.5 out of 100. Its strongest areas are configuration management depth, scale and control plane. Its weakest are ai assistance, provisioning breadth, bare metal and day-2 operations.

    What are the best alternatives to Salt?

    The closest by Ledger Index are MAAS (47.6), Juju (47.8), Chef (49.1), OpenVox (49.5).

    How is Salt licensed and sold?

    Engine licence unchanged; the commercial product was repackaged twice since 2023 and standalone sales ended in January 2024.

    How much lock-in does Salt bring?

    Salt scores 8 out of 25 on technical lock-in (lower is better). Export path: No conversion path to another tool; states and pillar need rewriting.

    User reviews of Salt

    No reviews yet

    Be the first to say how Salt worked for you.

    Write a review

    No account needed and no email asked. We read every review before it appears and remove adverts, spam and personal attacks.

    Your rating