Services
Cloud, AI, Identity.
Three distinct practices, which you can call on separately. Each is described below by the problem it answers and what we do about it.
Cloud organisation governance
The move to cloud is done. What remains is holding it together.
Accounts and projects have multiplied, every team has its own rules, and nobody can state what is allowed any more. The question is no longer how to migrate: it is how to govern, secure and lay out what exists.
What we do
- Landing zones and the account model: who owns what, and where a new team goes
- Guardrails and organisation policies, written as code and tested
- Security and compliance by design: NIS2, DORA, encryption, backup
- Layout: network, regions, and disaster recovery that is rehearsed
- Cost control, with no standing cost where none is needed
Platforms
- AWS: Organizations, SCPs, landing zones
- Google Cloud: organisation, folders, organisation policies
In practiceGoverning an AWS organisation of more than a thousand accounts →
AI deployment
AI does not enter a team through a licence.
The licences are bought and usage does not follow: everyone tries things alone, security holds back, and nothing scales. We work inside your teams, as forward deployed engineers, until AI is part of how the work gets done.
What we do
- Finding the needs and the workflows worth handing to AI
- Setting up the harness: skills, agents and plugins, on your repositories and your tools
- AI governance: who may do what, on which data, with what audit trail
- AI security: guardrails, evaluation and non-regression
- Handover: your teams own what was built
Tools
- GitHub Copilot
- Claude
In practiceGoverning an AWS organisation of more than a thousand accounts →
Identity management
Knowing who, and what, has access to what.
Service accounts with no owner, secrets copied from one repository to the next, access that outlives a departure. The identities of people and those of machines are managed together, or not at all.
What we do
- People: federation and single sign-on with Entra ID
- Machines and secrets: HashiCorp Vault and short-lived credentials
- Brokered, least-privilege access to databases and cloud platforms
- Lifecycle: joiners, leavers, rotation and revocation
Technologies
- HashiCorp Vault
- Microsoft Entra ID
In practiceMigrating to AWS with disaster recovery the business can audit →
How we work with you
Audit
A review of where you stand and a prioritised roadmap, presented to your leadership.
Fixed-scope project
A scope, a deliverable, and milestones agreed in advance.
Embedded architect
A senior architect inside your team: design authority, reviews and hands-on coaching.
A project, a doubt, an audit to prepare?
Describe your need