Puppet Enterprise is Perforce's commercial configuration management platform; since 2025 even open-source Puppet binaries come from Perforce under a EULA. Pages here cover replacing it with OpenVox, the community fork.
Puppet Enterprise against the OpenVox community fork: language and module compatibility, what Enterprise adds (console, orchestration, RBAC, support), what OpenVox ships (agent, server, OpenVoxDB, OpenBolt), governance under Vox Pupuli and the risk of drift from Perforce's Puppet.
Moving nodes and servers from Puppet Enterprise to OpenVox: backing up /etc/puppetlabs, running the PE uninstaller, installing openvox-server, OpenVoxDB and agents from the Vox Pupuli repositories, keeping certificates and code, and replacing the PE console and orchestrator.
Cost of ownership by component: quoted Puppet Enterprise or Puppet Core Commercial licenses above 25 nodes against OpenVox's free packages, the servers and PostgreSQL behind OpenVoxDB, a replacement for the PE console, migration, and the support you arrange yourself.
Since early 2025 new Puppet packages come from a private repository, free under a development EULA up to 25 nodes and licensed above that. This page sets out the options: pay for Puppet Core, stay on old public packages, or move to OpenVox.
Puppet Enterprise 2023.8 maintenance ended August 27, 2026, and support ends February 27, 2027. This page compares upgrading to the Latest track, which gives each major version 12 months of full support, with moving to OpenVox before the deadline.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.