config.XO vs LCFG

config.XO extends Microsoft PowerShell Desired State Configuration to manage Windows and Linux node configurations. It evaluates managed servers and clients against their intended state and corrects drift automatically. Teams can assign configurations to groups or individual hosts, create their own configurations and modules, or use a web wizard to build DSC configurations without writing code. It supports on-premises physical hosts and virtual machines, as well as internet-connected public-cloud virtual machines; proxy configuration is possible. Listed Windows versions are Server 2022, 2019 and 2016, plus Windows 11 and 10. Configuration runs can install packages through application.XO. The cloud service is agent-based and lists patch management, policy as code and compliance reporting alongside drift detection. Uploaded DSC configurations are encrypted with an XOAP-provided certificate, but user-uploaded compiled MOF files are not encrypted. XOAP says its service is hosted in Europe, is GDPR compliant, encrypts management connections and does not store actual user credentials. Free includes three managed systems; Standard is €449.00 per month or €4,999 billed annually.

LCFG is a free, GPL-licensed system for automatically installing and managing configurations across large groups of Unix machines. It targets sites where systems differ and change frequently. Administrators keep source settings on a central server; LCFG compiles them into XML profiles that clients download when changes occur. Client components react to resource changes by generating configuration files and reconfiguring related daemons. A package component aligns installed software with each machine’s profile. New machines can be installed over a network file system after source files are created, using a boot floppy or PXE. LCFG is self-hosted and agent-based, with patch management and HTTP resource transport. Listed supported platforms include Ubuntu 20.04, 22.04, and 24.04; FAQ material also names Fedora Core 3, 5, and 6 and Scientific Linux 5. Solaris support is weaker and un-packaged, Mac OS X is experimental, and the demonstration Windows client lacks real components. Documentation covers configuration, dynamic networking, and build tools.