- Challenge
- Projects and permissions have sprawled. That was how the client put it on the first call.
- Approach
- We restructured projects and permissions, put networking and GKE into Terraform, and set an upgrade schedule with the team.
- Stack
- Resource Manager · IAM · GKE · Terraform
- Result
- Projects and access are tidy, and cluster upgrades happen on a calendar.
Google Cloud: Projects, networking and data services built to last.
From projects, IAM and networking to running your apps, data and pipelines: we set it up properly, keep it running and document it for your team.
Talk to an engineerWhat we do
Google Cloud consultancy
An assessment of your Google Cloud setup, with findings ranked by risk and effort.
Google Cloud delivery
We design and build it with your team, in your accounts, documented as we go.
Google Cloud support
Monitoring, patching and upgrades, with incident response agreed per contract.
Google Cloud training
Workshops and pairing on Google Cloud, built around your own systems.
Tools we work with
Identity & governance
- Resource Manager
- Cloud IAM
- Organization Policy
- Cloud Identity
Compute & containers
- Compute Engine
- Managed Instance Groups
- Cloud Run
- Cloud Functions
- GKE
- Artifact Registry
Networking & delivery
- VPC
- Cloud Load Balancing
- Cloud CDN
- Cloud DNS
- Cloud NAT
- Cloud VPN
- Interconnect
Data & storage
- Cloud Storage
- Persistent Disk
- Filestore
- Cloud SQL
- AlloyDB
- Spanner
- Firestore
- BigQuery
- Pub/Sub
Security
- Secret Manager
- Cloud KMS
- Security Command Center
- Cloud Armor
- IAP
Operations & cost
- Cloud Monitoring
- Cloud Logging
- Cloud Trace
- Backup and DR
- Billing reports
Delivery & infrastructure as code
- Cloud Build
- Cloud Deploy
- Terraform
- Terragrunt
- OpenTofu
How an engagement runs
- 1 A call. 30 minutes with an engineer to understand the problem.
- 2 A look. Read-only access or a walkthrough, so we scope from facts.
- 3 A proposal. Scope, deliverables and a price model: fixed scope, day rate or retainer.
- 4 The work. In your accounts and repositories, alongside your team.
- 5 A handover. Documentation and a session with your team, so you’re not dependent on us.
Proof
A recent Google Cloud engagement. We keep client names private, but the problem, the work and the outcome are exactly as they happened.
See our workQuestions
Do you work in our accounts or yours?
Yours. Everything we build lives in your cloud accounts and repositories from day one, so there is nothing to migrate when we finish.
Can you work alongside our own team?
Yes, and we prefer it. We can run a project ourselves, embed engineers in your team, or pair with your people so they pick it up as we go.
How is this priced?
Depending on the work: a fixed-scope price, a day rate or a monthly retainer. We agree it in a written proposal before anything starts.