Decolla vs SmartDeploy
Decolla and SmartDeploy both get Windows machines built and into users' hands, but they take fundamentally different routes: SmartDeploy deploys a golden image, while Decolla provisions devices natively through Microsoft Autopilot and Intune with no image at all. This page lays out where each genuinely wins, so you can pick by environment rather than by pitch. Decolla is in early access.
Two different philosophies of getting a Windows PC ready
SmartDeploy is a mature, image-based deployment tool (part of PDQ since 2022). You build a single hardware-independent golden image from a virtual reference machine, and SmartDeploy deploys that image to any make or model. Its standout engineering is driver handling: a patented boot-time driver injection process backed by a library of 1,500+ prebuilt, model-specific Platform Packs, kept logically separate from the image. You can deploy over USB, a network server, or cloud storage with no VPN, and manage apps, patches and in-place Windows 11 upgrades from a web console. It is a genuinely strong answer to the question "how do I put a known-good, fully built Windows image on lots of different hardware, including remote and offline machines?"
Decolla answers a different question: "how do I stand up and run Windows devices through Microsoft's own cloud, without maintaining an image at all?" You define the build as a written, itemised plan (a catalogue of 377 curated items across 29 sections: apps, policies, security baselines, compliance and migration), review it, then deploy it unattended through your own Autopilot and Intune tenant. There is no gold image to build, patch or re-capture. Every item it applies is reversible on its own and deployment is gated — nothing runs without explicit per-batch confirmation. Decolla runs inside your tenant using delegated Microsoft Graph consent and publishes the exact Graph scopes it requests before connecting.
Neither approach is universally better. The right choice depends almost entirely on whether you are committed to imaging and whether you have (and want to build on) a Microsoft Intune/Entra tenant.
How they differ
The table compares the two across the dimensions that usually decide the outcome. Where SmartDeploy is the stronger fit, it says so.
| Dimension | Decolla | SmartDeploy |
|---|---|---|
| Core approach | Autopilot/Intune-native provisioning from the device's factory/OEM state — no image | Image-based deployment of a golden Windows image to any hardware |
| Gold / reference images | None to build or maintain; configuration is applied as policies and apps through the tenant | Central to the model — build and maintain a hardware-independent image from a VM reference (a mature, proven workflow) |
| Driver handling | Left to Windows, the OEM and Intune; no driver packs to curate | A genuine strength — patented boot-time driver injection with 1,500+ prebuilt Platform Packs for mixed fleets |
| Review before change | A written, itemised build plan (377 items / 29 sections) is reviewed before anything runs | Image and pack contents are defined by the admin; changes are validated by re-imaging or updating packs |
| Reversibility | Per-item rollback — undo a single item without a wipe or rebuild | Typically roll back by re-imaging (OS layer or full machine) rather than per-setting |
| Needs Intune / Entra tenant | Yes — runs in your own tenant via delegated Graph consent | No — works independently of the Microsoft cloud |
| Deployment media | Cloud, unattended through the tenant | USB, network server, or cloud storage (Box/Dropbox/Google Drive/OneDrive/S3), no VPN |
| Offline / air-gapped | Not suited — needs tenant connectivity | Strong — USB imaging works with no cloud at all |
| Ongoing management | Cloud lifecycle — policy, compliance and security baselines managed continuously in Intune | Imaging-centric, plus app packs, patching, remote tasks and in-place Windows 11 upgrades |
| Platforms | Windows primarily; also iOS, Android and macOS via Intune | Windows-focused |
| Learning curve | Assumes Intune/Entra familiarity; the written plan lowers the review burden | Familiar to anyone with an imaging background; VM reference and packs are established concepts |
| Status / maturity | Early access | Established and widely used |
The honest headline: SmartDeploy owns the imaging story and the driver problem; Decolla owns the cloud-native, no-image, reversible-and-reviewable story. They overlap far less than the "deploy Windows" label suggests.
When to use which
Choose SmartDeploy when:
- You are committed to imaging and your team is happy with a golden-image workflow — there is no reason to abandon a process that works well for you.
- You don't have (or don't want to build on) an Intune/Entra tenant. SmartDeploy deliberately doesn't require the Microsoft cloud; Decolla does. If you have no tenant, Decolla simply isn't for you.
- You need to provision offline, air-gapped or bandwidth-constrained sites where booting from USB and imaging locally is the pragmatic answer.
- You run a mixed hardware fleet and value SmartDeploy's boot-time driver injection and large Platform Pack library — a real strength for putting one image on many models.
- Your bread and butter is break-fix reimaging — wiping a machine back to a known-good full state quickly, or reimaging just the OS layer to resolve a problem.
- You're provisioning a single one-off machine and don't want cloud tooling in the loop at all.
Choose Decolla when:
- You already run Autopilot and Intune (or intend to) and want to provision devices from their factory state without building or maintaining an image.
- You want the build expressed as a written, itemised plan you review before it runs, rather than inspecting the contents of an image.
- You value per-item reversibility — rolling back one setting or app without wiping and rebuilding the device.
- You care about the whole cloud lifecycle (policy, compliance and security baselines managed continuously in Intune), not just day-one deployment.
- You want a gated process that runs in your own tenant on delegated Graph consent, with the requested scopes published up front.
Where Decolla fits
If imaging is working for you — or you have no Intune/Entra tenant, or you provision offline — SmartDeploy is the sounder choice, and its driver management is a real advantage worth keeping. Decolla isn't trying to be a better imaging tool; it removes the image entirely for organisations that live in Microsoft's cloud.
Decolla's value is for teams already on Autopilot and Intune who want a written, reviewable plan, per-item rollback instead of reimaging, and gated, unattended provisioning inside their own tenant — spanning the full device lifecycle, not just the first build. Decolla is in early access; if that matches your environment, it's worth a look, and if it doesn't, an imaging-first tool like SmartDeploy is the honest recommendation.
See it on a real device.
Decolla is in private build — early-access members see a build defined, deployed and rolled back first.
Get early access