Puppet alternative for Windows and Linux fleets
Gardience is a Puppet alternative for teams leaving Puppet after Perforce's license change. It runs on the open-source Salt agent, declarative and agent-based like Puppet, and adds Windows and Linux patching, DISA STIG checklists for Linux, CMMC Level 2 evidence, and two-person approval at a flat yearly price. It does not run Puppet manifests: you move them to Salt states one role at a time.
- 25nodes: reported limit before Perforce's Puppet builds need a license
- $15,000a year at 1,000 machines, Windows and Linux
- 20Windows and Linux platforms verified on real machines
- 1,020servers patched in 13 minutes, one approved run
Puppet is a configuration management tool owned by Perforce since 2022: an agent on each machine pulls its configuration from Puppet Server on a schedule and corrects drift. In late 2024 Perforce moved new Puppet builds to a private repository, and the community forked the open-source code as OpenVox. Gardience is a fleet console on open-source Salt, the closest engine to Puppet's model, with patching, compliance, approvals, and evidence built in.
How does Gardience compare to Puppet and OpenVox?
#| Puppet (Perforce) | OpenVox | Gardience | |
|---|---|---|---|
| Who maintains it | Perforce | Vox Pupuli community | Gardience, on the open-source Salt Project |
| License | New builds from a private repository; use above 25 nodes reported to need a commercial license | Community builds of the Apache 2.0 code | Open-source Salt agent, commercial console at a flat yearly price |
| How it reaches machines | Agent pulls its configuration on a schedule (every 30 minutes by default) | Same as Puppet | Agent keeps a live encrypted connection; jobs reach the fleet in seconds |
| Language | Puppet's own declarative language | Same as Puppet | Salt states in YAML with Jinja; your Ansible playbooks run too |
| Windows | Native Windows agent | Native Windows agent | Native Windows agent: every Windows Server from 2016 to 2025, plus Windows 10 and 11 |
| Runs Puppet manifests | Yes | Yes | No: manifests move to Salt states over time |
What does Gardience add on the same agents?
#- Patching built in: Windows and Linux, pilot and broad rings, change windows, and second-person approval.
- CVE response: CVEs matched on every machine and ranked by CISA KEV and EPSS, fixed on only the exposed machines.
- DISA STIG checklists: on Windows Server, Windows 10 and 11, RHEL-family, SLES, and Ubuntu, weekly scans and a STIG Viewer checklist per machine for eMASS, plus a STIG/CIS-aligned baseline that is checked and fixed. See STIG automation.
- CMMC Level 2: covers all 110 requirements with a live SPRS score, SSP, POA&M, and a signed evidence pack.
- Drift repair and events: a stopped service is restarted within seconds, with both the drift and the fix on the record.
- A tamper-evident audit log of every change, who asked for it, and who approved it.
Why do teams move off Puppet?
#- The license changed. Reporting on Perforce's change says production use above 25 nodes needs a commercial license, and NC State noted no new releases in the public repositories as of July 2025.
- Changes wait for the next check-in. A Puppet agent converges on its next run; a Salt job reaches every connected machine in seconds and streams the results back.
- Patching and evidence live elsewhere. Configuration management is one tool; patching, CVE response, and the auditor's report are others. Gardience does all of it from one console.
Should you move to OpenVox or to Salt?
#OpenVox is the shortest step: keep your manifests, modules, and Hiera data, and swap the packages. Moving to Salt is more work and pays off when you want faster changes, first-class Windows, event-driven repair, approvals, and compliance evidence from the same agents. Salt states are declarative YAML, closer to Puppet manifests in spirit than procedural playbooks are. Our guide to open-source Puppet after Perforce walks through all four options.
How does a move from Puppet to Gardience work?
#- Install Gardience on any supported Linux server, in about five minutes, or fully offline.
- Enroll machines next to their Puppet agents. Both run side by side; nothing is removed.
- Patch and prove first. Patching, the security baseline, CVE matching, and STIG scans work on day one, with no states written.
- Move roles one at a time, starting with the ones you change most: write the Salt state from Git, test it on a pilot group, then stop managing that role in Puppet.
- Retire Puppet Server when the last role has moved.
Manifests cannot be converted to Salt states reliably by a tool, so plan a staged move rather than a cutover.
What does it cost?
#Starter is $6,000 a year for up to 250 machines and Team is $15,000 a year for up to 1,000, Windows and Linux alike, with no per-node charge. Enterprise starts at $40,000 for larger or air-gapped fleets. The free 90-day trial covers 25 machines. See pricing.
Questions
#Can Gardience run my Puppet manifests?
#Not today. Gardience runs Salt states and your existing Ansible playbooks over the Salt connection. Puppet manifests move to Salt states over time, one role at a time.
Is open-source Puppet still free?
#The source code remains under the Apache 2.0 license, but Perforce's packages come from a private repository, and reporting on the change says use beyond 25 nodes needs a commercial license. Check Perforce's current terms. OpenVox provides community builds.
Can Puppet and Gardience run on the same machines?
#Yes. The Salt agent and the Puppet agent run side by side, so you can move one role at a time and stop managing it in Puppet once the Salt state is proven.
Does Gardience manage Windows as well as Linux?
#Yes. The Salt agent runs natively on Windows, and Gardience adds Windows patching, a scored baseline, BitLocker, and approvals on top, in the same console as Linux.
Sources
#Checked November 7, 2026.
- DevClass on Perforce's Puppet changes and the community fork.
- NC State on the Puppet repository changes.
- The New Stack on OpenVox and Vox Pupuli's OpenVox page.
- Puppet by Perforce, for current terms.
Read more
- Open-source Puppet after Perforce: your options in 2026
- Salt vs Ansible for Windows servers
- Self-healing servers with event-driven automation
- GitOps for Salt: states in Git, the rest in Terraform
- Chef Infra licensing: what is free, what needs a license, and the Cinc option
Planning a move off Puppet?
Book a migration call and bring a manifest you change often. We map it to Salt states, show what changes, and plan a staged move that runs next to Puppet. Gardience Team is $15,000 a year at 1,000 machines.
Book a migration callThe Puppet migration planFree 90-day trial (25 machines)