Trust centre

Decolla runs inside your own Microsoft Intune tenant, which makes its behaviour your risk. This page sets out — in specifics rather than adjectives — how the product earns the right to be there.

Why this page exists

If you manage an Intune tenant, you are the person who answers for anything a third-party tool does inside it. That is the position this page is written for. Most vendor trust pages offer badges and adjectives; those are hard to evaluate and easy to manufacture. Decolla is a product of The Cloud Platform Ltd, currently in private build, and we have no customers or testimonials to point at — so the only honest way to earn your confidence is to document exactly how the product behaves, what access it needs, and where its limits sit. Each section below summarises one commitment and links to the full detail, so you can test our claims against your own standards before anyone asks you for anything.

The security model

Decolla provisions Windows devices over your own Microsoft Intune and Autopilot tenant — there is no parallel infrastructure holding your devices, and no multi-tenant management layer sitting between you and your estate. It connects through Microsoft Graph, and the full list of Graph scopes it requests is published before you connect, so you can review every permission against your security baseline rather than discovering it at the consent prompt. Nothing executes until you have read and approved an itemised written plan, and every item in that plan states its delivery method. Read the full security model.

The honesty page

There are claims we will not make, and we keep a page that lists them. The largest one: Decolla does not make Windows installs faster. Application installs, the Enrollment Status Page and policy sync all run at Microsoft's pace, in your tenant, and no overlay changes that. What Decolla compresses is the work before the build — choosing, testing and assembling the policies, scripts and fixes that make a build good. That is where weeks of DIY assembly normally goes, and where a curated, industry-tested library of 260+ build items changes the economics. Defining a build takes minutes; the deployment itself takes as long as Microsoft takes. Read the honesty page.

The reversibility promise

Before anything runs, every item in your plan carries one of three reversibility classes: auto (Decolla reverses it automatically), reverse (a documented reversal exists), or irreversible — flagged in plain sight so you approve it knowingly rather than by accident. After deployment you can roll back a single item or the whole build. The limit matters as much as the promise: rollback covers Decolla's own changes only. It cannot rescue a failed Microsoft install or a stuck Enrollment Status Page, and we would rather tell you that here than have you discover it during an incident. Read the reversibility promise.

Who builds this

Decolla is built by The Cloud Platform Ltd, a working UK IT consultancy. The Library — the catalogue of 260+ pre-built, industry-tested build items across 21 sections — comes out of that practice: the recurring, mundane helpdesk fixes, the hardening steps, the OEM tooling decisions by make and the power settings by chassis that every build needs and every engineer otherwise rebuilds from scratch. We are practitioners packaging work we already do, not outsiders discovering endpoint management from a pitch deck. Read about The Cloud Platform.

Where Decolla stands today

Decolla is in private build. There is no self-service sign-up, no published pricing, and — because we have no customers yet — no testimonials, logos or case studies, and you will not find manufactured versions of them here. The only thing on offer is early access: a place on the waitlist, and the chance to evaluate the security model, the plan format and the rollback behaviour against your own tenant's standards before you commit to anything. If the specifics on this page hold up under your scrutiny, that is the next step.