CFEngine vs LCFG

CFEngine automates infrastructure, security, and compliance by moving managed systems toward a state defined in policy. Users describe desired infrastructure states in CFEngine’s domain-specific language, and lightweight agents work to bring each device into compliance. By default, an agent contacts the CFEngine hub every five minutes. The system runs on embedded devices, servers, cloud systems, and mainframes, and is designed for tens or hundreds of thousands of nodes. Enterprise adds the Mission Portal web interface, reporting backed by an SQL database, REST APIs, compliance reports, policy analysis, alerts, inventory and change reporting, file-integrity monitoring, and performance monitoring. Dashboards provide compliance and performance views, alerts, and customizable sharing. Secure bootstrap uses mutual authentication, key exchange, and encrypted TLS communication. Community Edition is free under GNU GPL, supports Linux, and includes community support. Enterprise is free for up to 25 hosts; pricing beyond that is available on request. The supported operating systems listed include Linux distributions and Windows.

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.