config.XO vs OpenDSC

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.

OpenDSC is a configuration management platform for Microsoft Desired State Configuration, intended for teams managing settings across infrastructure nodes. Its Local Configuration Manager monitors system state and can automatically correct configuration drift. For centralized management, the pull server registers nodes, distributes configurations, and provides compliance reporting through a web dashboard and REST API. Configurations can be versioned, assembled into composite deployments, and parameterized by region, environment, or node. Local file-based configurations support disconnected use as well as server-driven pulls. The resource library covers Windows administration, SQL Server, and file, JSON, XML, and archive tasks across Windows, Linux, and macOS. The Resource Development Kit provides .NET libraries and tools for developing custom resources. The pull server supports OpenID Connect providers, client-certificate mutual TLS, role-based access control, and retention policies. SQLite is supported for development, while production deployments can use SQL Server or PostgreSQL. The project is MIT licensed and self-hosted. Its roadmap lists native Linux and macOS LCM services, distribution packages, and official Docker deployment as planned work.