Born on the tools
Decolla is built by The Cloud Platform, a working UK IT consultancy. Our products begin as jobs done by hand on real estates — this page explains why that matters for yours.
A consultancy first, a product company second
The Cloud Platform Ltd is a working UK IT consultancy. Not a former one, and not a product startup with a consulting page kept up for credibility — a consultancy that still takes on estates, still does the hands-on Intune and Autopilot work, and still gets the call when a device build goes wrong the week the new starters arrive.
That matters because of how our products come to exist. We don't start with a market thesis and work backwards. We start with a job we have done by hand enough times to know exactly where it hurts, then build the tool we wished we'd had while doing it. Decolla is the first of those tools.
The job we kept doing by hand
Anyone who has stood up Windows provisioning across more than one organisation knows the pattern. The Autopilot enrolment itself is well-trodden. The pain is everything around it: deciding and assembling what the build actually contains. Baseline configuration, hardening, drive strategy, locale, OEM tooling for whichever make arrived on the purchase order, power settings that make sense for a laptop but not a desktop, and the dozen small fixes you know from helpdesk experience will otherwise generate tickets in week two.
Every estate needs a version of that list. And almost every IT team assembles it from scratch — blog posts, community threads, scripts inherited from a predecessor, trial and error on a sacrificial laptop. It adds up to weeks of careful, mundane assembly work, and it is largely the same weeks everywhere.
Having done that assembly by hand across real estates, we concluded it was not a knowledge problem. It was a packaging problem.
What the day job put into the product
When practitioners design a provisioning tool, the scar tissue shows up as features. Some decisions in Decolla that came straight from consulting work:
- It runs over your own tenant. Decolla provisions through your own Microsoft Intune and Autopilot tenant. Your devices, your policies, your data boundary. We have sat through enough security reviews to know that any answer other than "your tenant" is a very long conversation.
- Nothing runs before you have read the plan. The guided wizard moves through Discover and Configure, then a curated catalogue of 260+ build items across 21 sections — filtered for relevance and intelligently defaulted by a conditional engine (OEM tooling by make, power by chassis, drive strategy, locale, existing-versus-new estates). The output is an itemised written plan. Every item states its delivery method and its reversibility class, with anything irreversible explicitly flagged. You approve the plan before anything touches the estate; only then does the deployment run unattended.
- Rollback is scoped honestly. You can roll back a single item or the whole build — for Decolla's own changes. It will not undo a failed Microsoft install or rescue a stuck Enrollment Status Page, and we won't pretend otherwise.
- Permissions in the open. The Graph scopes Decolla requests are published in full before you connect. You should not have to consent first and audit later.
The Library, and what the speed claim actually covers
The Library is the consultancy heritage made tangible: pre-built, industry-tested policies, scripts and fixes — including the recurring, mundane helpdesk fixes and the hardening steps that belong in every build but rarely make it into the first one. These run through Decolla's own mechanisms rather than bolted-on third-party tooling. The assembly work that takes weeks by hand happens in seconds.
To be precise about what that covers: the speed is in assembling and defining the build. Once your approved plan deploys, the installs run in your tenant at Microsoft's pace — Decolla does not, and cannot, make Intune install applications faster or move enrolment along quicker. Anyone telling you otherwise is selling you something else.
Product #1, and what we won't claim yet
Decolla is the first product in what will become a suite of utility applications from The Cloud Platform — each one a specific admin job we have done by hand, packaged properly. One tool, one job, done well.
It is currently a private build. That means some things you would rightly expect from a page like this do not exist yet: there are no customer logos, no testimonials, no case-study figures. Rather than invent them, we are saying so plainly and letting the design of the product make the argument — the written plan, the flagged irreversibles, the honest rollback scope, the published permissions.
If you own the risk for a Windows estate and this reads like tooling built by people who have carried that risk too, the early-access waitlist is where it starts.
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