Decolla vs Recast
Decolla and Recast are often mentioned in the same breath, but they solve different problems at different points in a device's life. Decolla governs and provisions the first build; Recast manages and orchestrates devices once they already exist. Here is an honest comparison so you can see which layer you actually need — or whether you need both.
Two different layers
Most comparisons assume two tools are fighting over the same job. Decolla and Recast are not. They sit at different layers of the Windows device lifecycle.
Decolla is a provisioning layer. It turns a bare, reset or freshly imaged machine into a governed, Intune-enrolled device — working from a written, reviewable build plan, and able to run entirely offline from a USB stick when a site has no reliable network.
Recast operates once the device already exists. Its two products manage and orchestrate the estate day-to-day: Application Workspace delivers identity-based application “playlists” at first sign-in, and Right Click Tools adds device management and remediation inside the Microsoft Intune admin center.
Read that way, the honest question is rarely “which one wins” — it is “which layer am I buying for”, and the two can be complementary.
How they differ
The table below sets the two side by side across the decisions that usually matter to a Windows admin. Where Recast is the stronger option, it says so.
| Capability | Decolla | Recast |
|---|---|---|
| What layer it operates at | First build and provisioning — a bare or reset machine becomes a governed, enrolled device. | After the device exists — application orchestration at sign-in and day-two device management or remediation. |
| Offline / USB | Whole-machine provisioning from a USB stick, including driver injection, for sites with little or no network. | No offline USB provisioning path; both products assume an existing, networked, enrolled estate. |
| Whole-build plan | A written, itemised build plan (currently 377 items) that a human reviews and approves before anything is deployed. | Ordered application “playlists” at sign-in; no single pre-deploy, human-reviewable plan for the whole machine. |
| Per-item reversibility | Every item in the plan is individually reversible; deploys run dry-run by default behind a triple gate. | Right Click Tools offers device remediation actions, but not per-item rollback of a whole build. |
| Agent / server footprint | Cloud-native and agentless at runtime; runs through your own Intune/Autopilot tenant and leaves nothing persistent behind. | Application Workspace needs a persistent agent on every endpoint, its own backend, and a per-user recurring licence; Right Click Tools’ full power needs the ConfigMgr agent and an on-prem or hosted Recast server, and drops to limited functionality on cloud-only, Entra-joined devices. |
| App orchestration | Packages and deploys a reviewed set of applications as part of the build; no per-user persona logic. | Stronger here — purpose-built for identity-based app orchestration and user personas at first sign-in. |
| Ongoing patching | Focused on the governed first build; not a continuous third-party patching engine. | Stronger here — mature ongoing management with third-party patching and remediation after enrolment. |
| Maturity | Early access. | Two mature, PE-backed products with a large proven estate (Recast cites a 65-million-device track record) and a G2 rating around 4.8. |
A note on accuracy: Recast is sales-led and quote-gated, so there is no public list price to compare against. We have also deliberately avoided repeating unverified performance or app-cap claims that circulate about either product — the real differences are the ones set out above.
When Recast is the better choice
A comparison that only flatters one side is useless in a bake-off. There are clear situations where Recast is the right call:
- Sophisticated app personas. If you need identity-driven application “playlists” — different app sets, ordered per user or role at sign-in — Application Workspace is purpose-built for exactly that.
- Continuous third-party patching. For ongoing patch and remediation of third-party software across the estate, Recast is a mature engine; Decolla is not.
- VDI and macOS breadth. Recast reaches further across virtual-desktop and macOS scenarios than Decolla does today.
- Live remote troubleshooting. Right Click Tools’ real-time device actions and remote support inside the admin center are a genuine day-two strength.
- A large, proven estate. If maturity and track record are the deciding factor, Recast has both; Decolla is early access.
If any of these is your primary need, Recast — or Recast alongside Decolla — is the honest recommendation.
Where Decolla fits
Decolla earns its place at the start of the device lifecycle, where the priority is a governed, auditable, reversible first build:
- A build you can read before it runs. The itemised plan is approved by a human up front, so nothing is deployed that no one reviewed.
- Reversible by design. Per-item rollback and a dry-run-default deploy behind a triple gate mean mistakes are contained, not catastrophic.
- Offline when you need it. Whole-machine USB provisioning with driver injection reaches sites and devices that a cloud-only, always-networked approach cannot.
- Nothing left behind. It is cloud-native, agentless at runtime, and runs through your own Intune/Autopilot tenant — no persistent third-party agent, no separate server to host.
Decolla governs how a device is born; Recast manages how it lives.
If you are choosing a provisioning and governance layer, Decolla is built for that job. If your first-build story is already sorted and you need day-two app personas, patching and remote support, Recast is strong. Many estates will want both — Decolla to stand devices up cleanly, Recast to run them afterwards.
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