Canonical Landscape vs LCFG

Canonical Landscape manages Ubuntu desktops, servers, cloud instances, IoT devices, and other Ubuntu systems from a central portal. Administrators can handle updates, packages and repositories, run scripts remotely, set role-based access, and monitor machines. It can alert on updates and graph temperature, disk and memory use, system load, and custom metrics. One instance can manage up to 40,000 machines, with options to scale further. Deployment choices are Canonical-hosted SaaS, Managed Landscape, and self-hosted software; SaaS is bundled with Ubuntu Pro. A free SaaS account with Ubuntu Pro covers up to five machines. Managed Landscape costs $6,861 a year per physical machine on public clouds, VMware, OpenStack, or LXD, or $9,470 a year per physical machine on bare metal. No self-hosted price is listed; Ubuntu Pro is its main licensing mechanism. Landscape has a scriptable API and can integrate with configuration management, monitoring, and ticketing systems. Self-hosting requires the organization to install, host, and maintain it. SaaS does not currently offer repository mirroring or custom external identity-provider configuration.

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.