DriverKit

DriverKit
Name	DriverKit
Developer	Apple Inc.
Released	2019
Operating system	macOS
License	Proprietary

DriverKit is a modern device driver framework introduced by Apple Inc. to move many kernel-resident drivers into user space on macOS, aiming to improve system stability and security. It reorients driver development away from traditional kernel extensions toward a user-space service model that integrates with macOS subsystems such as I/O Kit, System Extensions, and the Kernel Authorization framework. The framework has implications for developers who historically used I/O Kit in kernel space, and it interacts with technologies from Apple like Xcode, Swift, and the Apple Developer ecosystem.

Overview

DriverKit was announced by Apple during an Apple Inc. developer event and documented across Apple Developer resources, aligning with platform transitions such as the move to Apple Silicon and tighter security controls in macOS. It complements System Extensions and the Notarization requirement enforced by Apple, and it shifts many driver responsibilities previously handled by I/O Kit kernel extensions toward user-space daemons managed by launchd. DriverKit's creation intersects with corporate policies at Apple and broader platform strategies evident in macOS releases like Catalina and later. The framework affects device vendors, third-party hardware makers, and chipset producers who integrate with macOS hardware interfaces supported by Apple frameworks and Xcode tooling.

Architecture and Components

DriverKit’s architecture separates driver logic into user-space driver processes that interact with macOS kernel services via a new runtime API family and entitlements controlled through the Apple Developer Program. Core components include the DriverKit runtime, matching and lifecycle services that relate to I/O Kit matching dictionaries and IOService semantics, and the driver personality descriptions that echo concepts from I/O Kit. Interaction points and dependencies reference macOS subsystems such as launchd, DriverKit’s user client interfaces, and system logging services like Unified Logging used across Apple platforms. Subcomponents and supporting technologies include Xcode build tools, the Apple System Configuration framework, and device communication layers similar to those used by existing kernel extensions.

Development and APIs

Development uses Xcode and the Apple Developer tools with SDKs that expose DriverKit APIs, Objective-C and C headers, and evolving Swift bindings managed within Apple’s ecosystem. Developer workflows integrate with the Apple Developer Program for provisioning profiles, entitlements, and code signing required by notarization and system extensions. The APIs mirror many I/O Kit interfaces but are redesigned for the constraints of user-space execution, utilizing mach messaging and mach service names for interprocess communication and relying on kernel-provided bridged APIs when necessary. Tooling and examples are published through Apple’s documentation and sample code distributed alongside macOS SDK updates in Xcode, which developers reference when porting drivers from legacy kernel extensions.

Compatibility and Limitations

DriverKit is constrained by Apple’s platform compatibility policies and hardware architecture transitions such as the move from Intel to Apple Silicon, affecting which classes of drivers are eligible for migration. Certain low-level operations that require direct kernel access remain unsupported, maintaining the need for legacy kernel extensions in rare cases or driving hardware makers to redesign firmware and device behavior. The framework imposes limitations tied to entitlements and notarization enforced by Apple, and compatibility matrices are published by Apple for supported device classes, macOS versions, and chipset families, which hardware vendors and integrators must consult during porting efforts.

Security and Sandboxing

Because drivers run in user space under DriverKit, they inherit many security benefits from macOS user-space protections, including process isolation, sandboxing mechanisms similar to those used by System Extensions, and reduced risk of kernel panics compared to kernel extensions. DriverKit integrates with macOS security features such as code signing, entitlements, App Sandbox-like controls when applicable, and system-level audits performed via Apple’s security review processes in the Apple Developer Program. The design reduces attack surface area by eliminating privileged kernel memory access for many classes of drivers, aligning with security hardening efforts seen in Apple platform initiatives and partnerships with hardware vendors and research communities.

Deployment and Distribution

Drivers built on DriverKit are packaged and distributed through mechanisms compatible with Apple’s ecosystem, including Installer packages signed with Apple Developer certificates, notarization workflows, and distribution channels used by hardware vendors, accessory makers, and enterprise device management solutions. Deployment models integrate with Mobile Device Management (MDM) solutions supported by Apple, enterprise provisioning controlled through Apple Business Manager, and user consent flows enforced by macOS privacy and security prompts. The distribution process requires adherence to Apple’s submission policies and code-signing requirements enforced by the Apple Developer Program and notarization systems.

Adoption and Examples

Adoption has occurred across a range of third-party peripheral makers, accessory manufacturers, and software vendors who previously used I/O Kit kernel extensions, including vendors of storage controllers, networking adapters, and specialty input devices that have migrated drivers to the user-space model. Notable ecosystems affected include peripheral hardware integrators, chipset suppliers, and major accessory brands that coordinate with Apple’s platform updates and SDKs. Migration case studies and example implementations have been shared by some vendors, Apple Developer Relations, and community projects that document porting strategies from legacy kernel extensions to the DriverKit model in the broader Apple hardware and developer ecosystems.

Category:Apple software