Os

OpenVox Server on Ubuntu 24.04 LTS

Azure Developer Tools

OpenVox, the fully open source configuration management server that keeps every node in the state you declared in code.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

OpenVox is the community maintained, Apache 2.0 licensed continuation of Puppet, and OpenVox Server is its server side component. It compiles catalogues from your manifests and serves them to agents, runs the certificate authority that gives every managed node a verifiable identity, and collects the facts and run reports those nodes send back. You describe the state a machine should be in, in code, and the agent makes it so on every run, correcting anything that has drifted, so rebuilds become routine and configuration drift is something you detect rather than discover. OpenVox speaks the Puppet language, so existing manifests, modules and Puppet Forge content apply unchanged and existing Puppet agents can report to it.

Why the cloudimg image

The cloudimg image is hardened and fully patched, with OpenVox Server and the OpenVox Agent installed together on one instance so the appliance proves itself on first boot by compiling a real catalogue and applying it. The JVM heap and JRuby pool are sized deliberately for the recommended instance size rather than left at upstream defaults, and no swap is used to make the stack fit. It ships with no default credentials and, crucially, with no certificate authority at all: first boot mints that instance's own certificate authority and host certificate bound to its own hostname, then opens the listener. Until that has happened the server stays bound to loopback and is held stopped by a bootstrap guard, and a start time identity check refuses to serve without a per instance authority. Every image is paired with a step by step deploy guide and backed by 24/7 cloudimg support.

Common uses

  • Define server configuration as code and enforce it continuously across a fleet
  • Detect and correct configuration drift instead of discovering it during an incident
  • Run a self hosted, fully open source control plane compatible with existing Puppet manifests and agents