How Decolla works

Decolla assembles zero-touch Windows provisioning over your own Microsoft Intune and Autopilot tenant — through a guided wizard, a written plan you approve before anything runs, and declared reversibility for everything it changes, with irreversible items flagged before you approve.

The problem isn't the platform — it's the assembly

Microsoft Intune and Windows Autopilot are capable platforms. That is not where the time goes. The time goes into everything you have to assemble on top of them: baseline policies, OEM tooling for whichever makes you happen to buy, power and drive decisions per chassis, locale settings, the hardening you know you should apply, and the same mundane fixes your helpdesk re-applies to every fleet. Most teams rebuild that stack by hand, from scattered notes and community threads, every single time.

Decolla is a product of The Cloud Platform Ltd, a working UK IT consultancy, and it exists to remove that assembly work. It builds zero-touch Windows provisioning over your own Intune and Autopilot tenant. It is not a replacement MDM and it does not take your devices anywhere else — everything it produces lands in your tenant, as your configuration.

Connect: your tenant, start to finish

The first step is connecting Decolla to your Microsoft tenant. The Microsoft Graph permissions Decolla requests are published in full before you connect — you can read every scope and decide before granting anything.

From that point on, the division of labour is fixed: Decolla assembles and orchestrates; Microsoft executes. Every policy, profile, script and assignment Decolla creates is a real object in your Intune tenant, visible and inspectable in your own admin centre, delivered by the same Microsoft machinery you use today. There is no shadow infrastructure and no parallel management plane.

Discover and pick: 260+ items, filtered to your estate

A guided wizard then walks the journey: Discover → Configure → Pick → Plan. Discover asks about your situation — platform, chassis types, deployment scenario, hardware makes — and a conditional engine filters and defaults the rest: OEM tooling matched to make, power behaviour matched to chassis, drive strategy, locale, an HVCI gate, and whether you are working in an existing tenant or a new one.

You then pick from a curated catalogue of 260+ build items across 21 sections, already narrowed to what is relevant and intelligently pre-selected. Behind the catalogue sits the Library: pre-built, industry-tested policies, scripts and fixes — including the recurring helpdesk fixes and hardening steps every fleet needs but nobody enjoys re-writing. Assembly that normally takes weeks of research happens in seconds, and defining a complete build takes minutes.

How Discover narrows the catalogue and what is inside the Library are each covered in detail on their own pages.

The plan: nothing runs until you've read it

Nothing deploys from a wizard click. The output of Pick is an itemised, written plan — every item listed, with two things stated against each: how it will be delivered and how reversible it is. Reversibility is classed explicitly — automatically reversible, reversible, or irreversible — and irreversible items are flagged, not buried.

If you are the person who owns the risk when provisioning goes wrong, this is the step built for you. You read the plan, you query it, you approve it — or you don't, and nothing happens. Automation you cannot review before it runs is a liability; Decolla's position is that the plan is as much the product as the deployment is.

Read more about the plan and its reversibility classes.

Deploy and roll back — with the caveats up front

On approval, deployment runs unattended in your tenant. Two honest caveats, stated here because you would find them anyway:

• Decolla does not speed up Microsoft. Windows installs, the Enrollment Status Page and Intune sync run at Microsoft's pace, exactly as they do today. The weeks Decolla saves are in assembly and decision-making, not in the install itself.
• Rollback covers Decolla's own changes only. You can roll back a single item or a whole build, and reversibility is declared in the plan before you approve. What rollback will not do is unwind a failed Microsoft install or rescue a stuck ESP — no tool can honestly promise that, so Decolla doesn't.

What deployment actually does and how rollback works — and where it stops each have a full page.

Where Decolla is today

Decolla is in private build. It comes out of The Cloud Platform Ltd's own consultancy work provisioning Windows estates, which is why the catalogue is full of the unglamorous items real deployments need rather than demo-ware. There are no customer logos or testimonials on this site because there are no customers yet — it has not launched, and we would rather show you a written plan than a borrowed quote.

Early access is by waitlist, and the waitlist is the only thing we will ask you to join. If a plan you can read before anything runs sounds like how provisioning should have worked all along, add your name below.