Compliance-ready, and built for every Windows you run

CtrlOne helps you prove compliance with one-click evidence packs and runs across Windows 10, Windows 11, and Windows Server - on every edition from Home to Datacenter.

Security compliance

CtrlOne exports audit-ready evidence packs that let you and your auditors assemble the proof a framework asks for - drawn from live audit logs, policy history, and device posture across your fleet.

ISO 9001:2015 evidence pack

Evidence pack aligned to quality-management requirements - documented processes, change control, and consistent configuration across the fleet.

ISO/IEC 27001:2022 evidence pack

Evidence pack that maps CtrlOne controls to Annex A information-security objectives.

ISO/IEC 27701:2019 evidence pack

Evidence pack supporting privacy information management - controlled access to systems that process personal data.

ISO/IEC 20000-1:2018 evidence pack

Evidence pack aligned to IT service management - change, configuration, and incident records for managed endpoints.

ISO 22301:2019 evidence pack

Evidence pack supporting business continuity - signed cached policy enforced offline and recoverable, versioned policy state.

Compliance-ready, not a certification. The ISO 9001:2015, ISO/IEC 27001:2022, ISO/IEC 27701:2019, ISO/IEC 20000-1:2018, and ISO 22301:2019 evidence packs help you demonstrate the controls your organization operates. They are not certifications held by CtrlOne or UQuick Technologies India Limited.

  • Tamper-evident, hash-chained audit logs
  • Role-based access control across five operator roles
  • Per-tenant SSO (SAML / OIDC) and API tokens
  • Encryption in transit with TLS 1.3 and certificate pinning
  • Policy versioning and one-click rollback
  • Multi-tenant isolation with per-tenant storage quotas

Supported operating systems

One signed agent covers the whole Windows family, on standalone and domain-joined machines alike - no Active Directory or on-prem server required.

  • Windows 11 - all feature updates (21H2 and later), all editions.
  • Windows 10 - version 1809 and later (21H2+ recommended), all editions.
  • Windows Server - 2016, 2019, and 2022 (Standard & Datacenter); Desktop Experience required for shell restrictions.

Compatibility matrix

Core restrictions, the auto-scheduler, and the cloud console work on every supported platform; application control depends on the Windows edition.

PlatformSupported buildsAgent & core restrictionsApplication controlSupport level
Windows 101809 - 22H2SupportedFeature-specific Windows policies; applicability varies by edition and buildPer feature
Windows 1121H2 - currentSupportedFeature-specific Windows policies; applicability varies by edition and buildPer feature
Windows Server2016 / 2019 / 2022SupportedFeature-specific Windows policies; Desktop Experience required for shell restrictionsPer feature*

* Windows Server: desktop-shell restrictions require the Desktop Experience feature. Server Core exposes a smaller UI surface.

Supported editions

CtrlOne runs on every mainstream Windows edition. The difference between them is how application control is enforced - everything else is consistent.

  • Windows Home - fully managed via direct registry-policy enforcement, no gpedit required; application control is feature-specific.
  • Windows Pro - Group Policy and registry enforcement; application control depends on what Windows supports for each feature.
  • Windows Enterprise - application-control features apply where Windows supports them.
  • Windows Education - application-control features apply where Windows supports them.
  • Windows Server - Standard and Datacenter, 2016 onward; Desktop Experience required for shell restrictions.

Known limitations

We would rather be clear up front than surprise you during a rollout. These are the boundaries of what CtrlOne does today.

  • Windows only - there is no macOS, Linux, ChromeOS, iOS, or Android agent.
  • Application control is feature-specific and depends on what Windows supports for each edition and build; not every catalogue entry applies to every OS.
  • Full enforcement requires the agent to run as a SYSTEM service; a standard-user-only install can read state but cannot enforce machine-wide policy.
  • Windows 7, 8, and 8.1 are end-of-life and are not supported.
  • Microsoft ended mainstream support for Windows 10 in October 2025. CtrlOne still manages Windows 10 devices, but running an out-of-support OS is a compliance risk worth planning your migration around.
  • The platform is validated on x64; ARM64 Windows should be piloted before a fleet-wide rollout.
  • On Windows Server, desktop-shell restrictions assume the Desktop Experience is installed; Server Core exposes a smaller UI surface.
  • Some restrictions take effect after an Explorer restart or the next sign-in; CtrlOne triggers this automatically where it can.