Build
Custom cloud training
Cloud training on the platform you actually run, using your own architecture as the worked example — for teams who have inherited an estate faster than they have learned it.
Duration
Two to five days, delivered as a programme or in blocks
Built on
ISO/IEC 27001 · cloud provider security baselines · CIS Benchmarks
Indicative price
On request
Who this is for
IT manager
Has an estate that grew faster than the team's knowledge of it.
Infrastructure or platform engineer
Learned the platform by fixing it, with gaps nobody has mapped.
CISO
Needs the people configuring the cloud to understand what they are exposing.
CFO
Is paying a cloud bill nobody can fully explain.
Most cloud problems are knowledge problems wearing a technical costume
Cloud estates are rarely built. They accumulate — a migration, an acquisition, a project that needed something quickly, a supplier who set something up and left. The people running the result frequently learned it by repairing it, which produces deep knowledge in some places and blank spots in others, and nobody has ever mapped which is which.
The consequences show up as three separate complaints that are actually one problem. Security findings that repeat, because the same misconfiguration pattern keeps being recreated. A bill nobody can explain, because nothing was designed with cost in mind. And a delivery bottleneck around one or two people who are the only ones who know how something works.
Vendor certification courses do not fix this, because they teach a reference architecture and your estate is not one. The useful training uses your own environment as the material: this is your network design, here is why that policy does what it does, this is what that identity can actually reach.
We teach on the platform you run, whichever it is, and we are not reselling any of them. Where the training reveals architecture problems — and it usually does — we hand you a list rather than quietly turning it into a consulting proposal.
How we do it
- 01
Knowledge baseline
3–5 days
What the team actually knows, mapped against what the estate requires. Done through conversation and practical tasks rather than a quiz, because people under-report gaps in a form.
- 02
Environment review
3–5 days
Your architecture, identity model, network design and cost structure, read well enough to teach from. Findings are recorded and given to you regardless of what the training covers.
- 03
Programme design
3 days
The modules that close the gaps that matter, sequenced. Where a vendor certification is genuinely the right answer for someone, we say so and stop.
- 04
Delivery
2–5 days
Hands-on, in a safe environment modelled on yours, with the real architecture on the screen for the discussion parts.
- 05
Runbook build
within the programme
Participants leave having written the procedures for the things they will actually do — starting the documentation that was missing.
- 06
Follow-up
30 days
One session after the team has applied it, to answer what came up. This is where the retention happens.
Named artefacts
What you receive
- Knowledge baseline by role, against the estate you actually run
- Architecture and identity findings, given to you in writing
- Programme design targeting the gaps that matter
- Hands-on delivery in an environment modelled on yours
- Runbooks written by the participants during the programme
- Cost-awareness module tied to your own bill structure
- Attendance and assessment records
- A thirty-day follow-up session
What we need from you
- Read access to the environment, or a representative copy. Teaching on a generic reference architecture defeats the purpose.
- Your actual cloud bill, if cost is in scope. Nothing focuses a platform team faster.
- Time for the follow-up session. Skipping it is the single biggest predictor of the training not sticking.
- Acceptance that the review may find things. We would rather tell you than teach around them.
What changes
- 01The team understands the estate they run, not a reference diagram.
- 02Repeating misconfiguration patterns stop being recreated.
- 03Documentation exists, because the participants wrote it during the programme.
- 04Cost is understood by the people whose decisions create it.
- 05The dependency on one or two individuals is measurably reduced.
What it costs
On request
All prices exclude VAT.
Questions
Which platforms do you teach?
The one you run. We are not a reseller of any cloud platform, so we have no incentive to steer you, and the programme is built around your architecture rather than a vendor curriculum.
Is this a certification course?
No. Vendor certifications are useful for individuals and widely available; this exists for a different purpose — a team understanding the specific estate it operates. Where someone genuinely needs a vendor certification, we will tell you and point you at it.
Can you train while we migrate?
Yes, and it is good timing: the architecture is being decided, and the team learns the target state as it is built rather than after. See the sovereign cloud migration engagement for the migration side of that.
What does it cost?
On request. Scoped on the number of participants, the days delivered and whether the environment review is included.
Leave with your top three risks documented
Thirty minutes with a senior practitioner. No slideware, no sales engineer.