What Decolla does not do

Most vendor sites tell you what a product does. This page tells you where Decolla stops — because if you own the risk of a deployment, the boundaries matter more than the brochure.

Why this page exists

You have evaluated tools before. The demo is flawless, the deck says "seamless", and somewhere around week three you discover what "seamless" quietly excluded. By then the purchase order is signed and the exclusions are your problem.

Decolla is built by The Cloud Platform Ltd, a working UK IT consultancy. We have sat on your side of that table, and we have inherited the tenants where the gap between the promise and the product became someone's very long Friday. So here is the list we would want to read before joining any waitlist. If something on it loses us your sign-up, that is the correct outcome — better here than in a support ticket six months in.

We do not make Microsoft's installs faster

Windows installation, application deployment, Intune sync and the Enrolment Status Page all run at Microsoft's pace. Nothing bolted onto a tenant changes that, whatever anyone's marketing implies. Decolla runs over your own Intune and Autopilot infrastructure, so the enrolment itself takes exactly as long as it takes.

When we say "minutes", we mean one thing only: defining the build. The part that normally consumes weeks — researching policies, writing scripts, testing configurations, packaging the same tedious fixes every fleet needs — is where the time actually goes, and that is what the Library collapses. Picking from 260+ pre-built, industry-tested items and approving a written plan takes minutes. The device still enrols on Microsoft's clock.

If a vendor tells you they accelerate ESP or app installs, they are describing a process they do not control. Ask them how.

We cannot un-stick a stuck ESP

When the Enrolment Status Page hangs, that is a conversation between the device, your tenant and Microsoft's service. No third-party tool can reach in and rescue it mid-flight, and we will not pretend Decolla can.

What we can honestly say is narrower: a good portion of enrolment misery is self-inflicted through configuration assembled under deadline pressure. Decolla's conditional engine defaults each build item deliberately — OEM tooling matched to the make, power configuration to the chassis, drive strategy, locale, the HVCI gate, existing-versus-new device handling — and every choice sits in a plan you read before anything runs. Fewer improvised decisions means fewer avoidable failure modes. But when the platform itself stalls, it stalls, and the fix lives with Microsoft, not with us.

Rollback means our changes — not Microsoft's failures

Decolla can roll back per item or roll back a whole build. The scope is precise: Decolla's own changes only. Before you approve a plan, every item declares its delivery method and its reversibility class:

• Auto — reversed cleanly by Decolla itself.
• Reverse — reversible.
• Irreversible — flagged plainly, in the plan, before you say yes.

What rollback does not cover: a failed Microsoft install, a broken enrolment, a stuck ESP, or anything changed outside Decolla. We cannot un-ring bells we did not ring. If another vendor offers "full rollback" of a Windows device, it is worth asking them to define "full" — the honest answer is always a subset, and we would rather publish ours than let you discover it during an incident.

One tenant at a time. No live telemetry theatre.

Decolla operates in your tenant — your Intune, your Autopilot, your control. There is no multi-tenant console and no MSP management layer today, and we will not sell you one that does not exist. If you manage many customer tenants, Decolla in its current form is not built for that, and you deserve to know before you invest evaluation time.

We also make no live build-telemetry claims. Deployment runs unattended in your tenant; we do not stream Microsoft's internals to a reassuring dashboard, because a progress bar over a process we do not control would be decoration, not data. The transparency Decolla offers sits earlier, where it is real: an itemised written plan you approve before anything executes, with the Graph scopes we request published in full before you ever connect.

What that leaves — and why we still think it earns your time

Strip away everything above and what remains is the part of provisioning that genuinely was your problem to solve by hand: assembling the build. The Library holds 260+ pre-built items across 21 sections — policies, scripts, hardening, and the recurring mundane helpdesk fixes every estate accumulates — industry-tested and filtered to what is relevant for your platform, chassis and scenario. Weeks of DIY assembly becomes seconds of selection, with a plan you read, an approval you give, and a rollback scope you understand exactly.

Decolla is in private build, and the early-access waitlist is the only thing on offer right now — no case studies, no testimonials, because there are no customers yet, and inventing some would rather undermine a page like this. If the boundaries above are dealbreakers, we have saved us both a call. If they read like the first honest scoping document you have seen from a vendor in a while, the waitlist is below.