Managed Platform Engineering
Every change traceable, every team on the same path. Faster delivery, proof for your auditors, and safe room for AI to help. We set it up with you and run it for you.
Every change traceable, every team on the same path. Faster delivery, proof for your auditors, and safe room for AI to help. We set it up with you and run it for you.
Problem
Every team, every supplier and now every AI coding assistant builds things its own way. The same environment exists in three versions, a production change was made by hand on a Friday, and when the auditor asks who approved it, somebody starts digging through chat history. The tools are rarely the problem. Nobody wrote down what good looks like, what is not allowed, and who is responsible for what.
What You Get
Not a tooling project. One agreed way to build and change things, and proof that it was followed, with a partner who keeps it that way.
Who changed what, when and with whose approval. Ready for ISO 27001, NIS2 and DORA questions.
Teams and suppliers start from the same proven templates instead of reinventing them.
Fewer manual steps, fewer surprises in production, and checks that run automatically.
AI assistants can write code, held to exactly the same checks as people.
Build and cloud spend tied to the project that caused it.
Everything lives in your own GitHub or Azure DevOps. We look after it; you own it.
Approach
Each step starts with a short project that sets things up, and continues with a flat monthly service that keeps it working. Take the steps you need, in the order that makes sense for you.
Step 1 · Direction
How you build and change things becomes a standing item on your leadership agenda, with someone in the room who knows the options.
Step 2 · Rules
What good looks like, what is not allowed and who owns which code. Written down, signed off, then checked on every change.
Step 3 · Foundation
Ready-made templates and automatic checks set up in your own GitHub or Azure DevOps, with the rules from step 2 built in. One project through the whole path before we leave.
Step 4 · In use
Templates age and projects drift. We keep each project up to date, checked and healthy, long after the launch.
There is no separate compliance add-on to buy. Rules, approvals and evidence are built into the templates, the checks and the day-to-day running.
New AI and data environments arrive the same way: as reviewed changes in your own repositories, held to the same checks as everything else.
How It Goes
Three phases. Most organisations have their engineering rules signed off within a month, and a working shared path a couple of weeks after that.
A few short workshops with your engineers and suppliers, and we write the document. What good looks like, what is not allowed and which code you are actually responsible for.
Which practices you adopt, and the naming and version rules everyone follows.
Who may change what, and who has to approve before production.
Which rules only warn, which block a change, and how exceptions work.
Every repository with an owner, and the builds you redo by hand most often.
Platform Governance ModelTemplates and automatic checks in your own GitHub or Azure DevOps, with one project taken all the way through.
For environments, networking and applications, with AI and data platforms when those follow.
Every change validated, checked, approved and recorded the same way.
The rules you agreed, checking every change.
Proof the path works, and the template for every project after it.
Platform Landing ZoneWe look after the path, the rules and your projects, as far as your tier goes.
Build capacity, templates and checks kept running and up to date.
Managed Platform FoundationRules kept current, every repository checked, evidence on every change.
Managed Platform GovernanceUpdates prepared, health and delivery speed tracked, drift caught early.
Managed Golden PathsRegular platform meetings and a quarterly brief, so the plan stays current.
Platform AdvisoryService Tiers
Every tier includes all four steps. The difference is how often we sit down with you: monthly, every two weeks or every week. Start where you are and move up when more teams build on the shared path.
Everything included, with a monthly rhythm. For organisations getting started.
Everything included, every two weeks. For organisations where several teams or suppliers build in the same cloud.
Everything included, every week. For organisations where releases happen every day.
Detailed Comparison
| Feature | Platform Essentials | Platform Standard | Platform Advanced |
|---|---|---|---|
| Direction | |||
| Meetings with your platform architect | Monthly | Bi-weekly | Weekly |
| Quarterly brief | Included | Included | Included |
| Quarterly review with your leadership | — | — | Included |
| Requests sorted, tools compared | Included | Included | Included |
| Rules | |||
| Rules kept current | Included | Included | Included |
| Every repository checked | Included | Included | Included |
| Exceptions and evidence of every change | Included | Included | Included |
| Build and cloud costs by project | Included | Included | Included |
| Foundation | |||
| Build capacity managed | Included | Included | Included |
| Templates and checks kept up to date | Included | Included | Included |
| Settings and permissions kept as agreed | Included | Included | Included |
| Monitoring and incident handling | Included | Included | Included |
| Your projects | |||
| Each project checked against the rules | Per project | Per project | Per project |
| Updates prepared for review | Per project | Per project | Per project |
| Health, delivery speed and drift tracked | Per project | Per project | Per project |
Every tier starts with a Platform Landing Zone and builds on a signed-off Platform Governance Model. Your projects are billed per project in every tier. Prices are starting points; your quote follows your scope.
FAQ
"Working with Cloud2 has allowed me to focus on developing code that is relevant to the business. Knowing that my partner will make sure that the cloud infrastructure where the code and services will eventually run is built and configured efficiently and, above all, securely."
Seppo Sormunen
Lead Developer, Digita
Field Notes
What we learn helping teams build the same way, safely.
Platform Engineering
6 min read
This blog is part of our Platform Engineering series. For a deeper understanding of our perspective on platform engineering, check out our other posts:
Platform Engineering
9 min read
This blog is part of our Platform Engineering series. For a deeper understanding of our perspective on platform engineering, check out our other posts:
Platform Engineering
6 min read
This blog is part of our Platform Engineering series. For a deeper understanding of our perspective on platform engineering, check out our other posts:
Start with the rules. In a few weeks you know what good looks like and what to set up first.
