OpenDSC
What it is
OpenDSC is a free, MIT-licensed, self-hosted configuration management platform for Microsoft Desired State Configuration. Its Local Configuration Manager monitors system state and can automatically remediate configuration drift. A pull server registers nodes, distributes configurations, and reports compliance through a Blazor dashboard and REST API. Configurations can be versioned, combined into composite deployments, and parameterized by region, environment, or node; local file-based configurations support disconnected use. The resource library covers Windows administration, SQL Server, and file, JSON, XML, and archive tasks across Windows, Linux, and macOS. Teams can create custom resources with the Resource Development Kit’s .NET libraries, CLI integration, and schema management. The pull server supports OpenID Connect providers including Microsoft Entra ID, Okta, and Auth0. Nodes authenticate with client certificates over mutual TLS, while role-based access controls provide users, groups, and granular policies. Administrators can set retention rules. SQLite is supported for development, with SQL Server or PostgreSQL for production. Native Linux and macOS LCM services, packages, and official Docker deployment are listed as roadmap work.
For and against
For
- Automatically remediates configuration drift
- Provides pull-server registration and compliance reporting
- Supports Windows, Linux, and macOS resources
- Offers REST API and Blazor dashboard
- Includes mutual TLS and role-based access controls
Against
- Self-hosted deployment is required
- Some native platform services remain roadmap work
- Production databases are SQL Server or PostgreSQL
- OpenDSC is agent-based
The verdict
OpenDSC combines local drift correction with centralized, API-accessible configuration management. Its security controls and cross-platform resources are substantial, while deployment remains self-hosted and some planned services are not yet listed as available.
Who it suits
It suits teams managing configuration policies across Windows, Linux, and macOS infrastructure nodes. It also fits centralized or disconnected deployments requiring compliance reporting and policy-based controls.
On the record
- Access control
- The Pull Server provides role-based access control with users, groups, and granular authorization policies.opendsc.dev · read 4 Oct 2026
- Access controls
- The pull server includes role-based access control with users, groups, and granular authorization policies.opendsc.dev · read 3 Oct 2026
- API and automation
- The pull server provides a REST API with interactive documentation for integration and automation.opendsc.dev · read 3 Oct 2026
- Configuration features
- Configurations can be versioned, combined into composite deployments, and parameterized by scopes such as region, environment, and node.opendsc.dev · read 3 Oct 2026
- Configuration options
- The LCM supports local file-based configurations for disconnected use as well as server-driven pull configurations.opendsc.dev · read 4 Oct 2026
- Cross-platform resources
- Its resource library covers Windows system management, SQL Server administration, and file, JSON, XML, and archive tasks across Windows, Linux, and macOS.opendsc.dev · read 4 Oct 2026
- Custom resources
- The Resource Development Kit helps teams build custom DSC resources and handles CLI integration and schema management.opendsc.dev · read 4 Oct 2026
- Database support
- The Pull Server supports SQLite for development and SQL Server or PostgreSQL for production deployments.opendsc.dev · read 4 Oct 2026
- Data retention
- Administrators can set global and per-configuration retention policies to remove old versions and control storage use.opendsc.dev · read 3 Oct 2026
- Deployment limits
- The install guide says Debian and RPM packages, Homebrew packages, and Docker support are coming soon.opendsc.dev · read 4 Oct 2026
- Drift correction
- Its Local Configuration Manager monitors configuration drift and automatically remediates divergence.opendsc.dev · read 4 Oct 2026
- Identity integrations
- The pull server supports OpenID Connect providers including Microsoft Entra ID, Okta, and Auth0, with JWT bearer tokens for API clients.opendsc.dev · read 3 Oct 2026
- Integrations
- The Pull Server supports OpenID Connect providers including Microsoft Entra ID, Okta, and Auth0, as well as standards-compliant OIDC providers.opendsc.dev · read 4 Oct 2026
- Intended users
- The documentation describes use for teams managing configurations across infrastructure nodes, including disconnected scenarios and centralized deployments.opendsc.dev · read 4 Oct 2026
- License
- The project’s GitHub repository identifies its license as MIT.github.com · read 4 Oct 2026
- License and maker
- The public GitHub repository identifies OpenDSC as MIT licensed, and the documentation credits Thomas Nieto.github.com · read 3 Oct 2026
- Management
- The Pull Server includes a Blazor web dashboard and REST API for node management, configuration assignment, and compliance reporting.opendsc.dev · read 4 Oct 2026
- Pull server
- The Pull Server centralizes configuration delivery, node registration, and compliance reporting.opendsc.dev · read 4 Oct 2026
