OpenVox: Infrastructure Automation Ledger 2026 Scorecard

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

Snapshot

• Type: community project (fork of Puppet by Vox Pupuli)
• Owner: Vox Pupuli, a volunteer collective with a Project Management Committee elected yearly; legal entity and funding not found
• Engine: the Puppet code base (agent, server, PuppetDB), with OpenFact in place of Facter since 8.22
• Licence: Apache 2.0; free, no node limit, no EULA; paid support through partners listed by the project
• Latest release: 9.1.0 and 8.31.0 (2026-10-13); 9.0.0 (2026-10-02)
• Support lifecycle: no written policy; OpenVox 7 packages ended July 2025; 8.x stays on Ruby 3.2 for its life
• Next milestone: OpenVox 10 (no date)
• Targets: the same hosts as Puppet (Linux, Windows, macOS); no Puppet Edge equivalent; no maintained modules for vSphere, Proxmox VE, Nutanix, Hyper-V, XCP-ng or KubeVirt
• Tier: Configuration management
• Archetype: Community continuation at upstream pace
• Evidence grade: B. Release dates were read from RubyGems, GitHub and the Vox Pupuli blog. Governance, legal entity and adoption are inferred or not found. The capability scores inherit the Puppet dossier where the code is the same.

Scorecard

Capability by domain, 2015 to today

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

Year by year: 2025: 50.4 · 2026: 52.4

What moved the score

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).

• Centre of gravity: Packaging (6), Licensing (2), Ecosystem (2)
• Blind spots (no items): Provisioning breadth, Configuration management, State and planning, Scale, Bare metal, AI
• Driver mix: Vision 8%, Customer need 46%, Market window 15%, Upstream 31%, Portfolio 0%
• Idea-to-need index: 0.11 (0 = demand-pulled, 1 = thesis-pushed)

Credibility: 16.5 / 25

Sustainability risk: 10.5 / 25 (lower is better)

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

Integrator fit: 8.5 / 20

AI leverage: 2.0 / 20

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

Year by year: 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 item has been announced.

OpenVox has announced no AI feature and has no MCP server. The agent path is the same Puppet Server and PuppetDB API as Puppet, without the Infra Assistant that Perforce ships in PE Advanced.

Reading

OpenVox exists because Perforce moved Puppet's supported builds behind an EULA in February 2025, and in twenty months it has turned a package mirror into a project with its own release pipeline, its own fact engine and a 9.0 on Ruby 4. The scores sit under Puppet's because the PE console, compliance content, patching and AI are not part of the fork. Its risk is sustainability: no legal entity or funding is on record, and security fixes now depend on the project's own work. A buyer should ask the support partner they intend to use for a written response time and check that their modules are tested against OpenVox.

Open questions and items to re-score

• Legal entity and funding behind Vox Pupuli and OpenVox.
• A written support policy; none was found.
• Whether the Puppet Standards Steering Committee with Perforce exists.
• Debian, Fedora and Ubuntu archive packaging; only Arch Linux, OpenBSD and ALT Linux packages were seen.
• openvox-server numbering: the first 9 series server release appears to be 9.0.1, not 9.0.0.
• Download or user counts; none were found.

Related reading

• Infrastructure Automation Ledger 2026 overview
• Proxmox automation
• Configuration drift: current environment against the approved baseline