The article
You moved to Google Cloud so that nobody on your team would have to look after servers. Cloud Run scales the app, Cloud SQL patches the database, and for a while the bill was small. So what is left for anyone to manage?
More than it looks. Google runs the machines and the database software; the settings, the access, the backups and the spending stay with you. Google Cloud managed services from a provider take over that second half. I have been building software for 18 years, and at 26 Lines of Code, a team of 70+ specialists, the engineers who would look after your Google Cloud projects work next to the developers who write the code running in them. Taking over that second half is one part of what we do in the cloud.
Google Cloud managed services: the short version
- What we run: Compute Engine, GKE clusters and Cloud Run services, Cloud SQL and storage, IAM roles and service accounts, monitoring and the bill.
- Who does it: named DevOps engineers, with developers from the same company when a problem starts in the app.
- How it starts: a review of your projects, then a plan with the price of running them.
- The bill: you pay Google, in your own account; the projects and the data stay yours.
- Our price: a monthly fee for an agreed list of work, named after the review; the first call and the rough estimate are free.
What Google runs, and what stays yours
Before paying anyone, look at the managed services Google Cloud already runs for you. Google publishes shared-responsibility pages for many of its services; this table simplifies them for six common ones.
| Service | Google runs | Yours, or your provider's |
|---|---|---|
| Compute Engine | The hardware and the virtualization under your virtual machines | The operating system and its patches, disks, snapshots, firewall rules |
| GKE | The control plane; in Autopilot mode, the nodes as well | Your workloads, their limits and access; in Standard mode, the node pools and their upgrade windows |
| Cloud Run | The servers, the scaling and the platform | The container: its base image and libraries, settings, secrets, who may call it and how far it may scale |
| Cloud SQL | The database software, vendor fixes in scheduled maintenance, the infrastructure underneath | Version, size and location, users and access, high availability, the maintenance window, tuning, storage headroom, backups and restore tests |
| Cloud Storage | Keeping what you store | Who can read each bucket, what is public, versioning and lifecycle rules |
| IAM and billing | The tools | Every role and service account, every budget and alert |
One detail in that last row is easy to miss: Google's billing documentation says an alerts-only budget does not cap usage or spending. A budget warns you; it does not switch anything off.
What we take on
Our Google Cloud Platform managed services cover the right-hand column:
- Compute Engine and the images behind it.
- GKE clusters and Cloud Run services, and the pipelines that deploy to them.
- Cloud SQL and storage, backed up and restored in tests.
- IAM roles and service accounts with only the rights they need.
- Monitoring and alerts that reach an engineer.
- Billing reviews, with idle resources switched off.
We agree the list before we start and keep a record of every change. In October 2026 I read three provider pages for this kind of work: the two Google Cloud pages in Google's top ten for this search and one that covers all three big clouds. None names a price, and none says whose account the projects and the bill sit in. Three pages are a small sample, but ask about both before you sign.
How it starts
- Review. Accounts, servers, networks, data and the code that uses them, written down.
- Plan. What we take over, what to fix first and what running it costs.
- Handover. Access, alerts and backups move to named engineers on our side.
- Running. Updates, fixes and cost reviews, with every change on record.
From you: access for the review, a list of what must never go down, and a yes to the plan and its price.
The developers are next door
When a problem in Google Cloud starts in the app - a slow query, a job that leaks memory, a key left in the code - a developer from the same company fixes it there, not only on the server. Two of our case pages show that side of the team, though neither names Google Cloud:
- Muzychko Vocal School was live on its first day and now runs 144 automated tests. Its looping video portraits jolted because the server ignored Range requests; a media view that answers with 206 responses, and posters cut from the video itself, fixed it in the code. An hour after the certificate was issued, a bot tried the admin 102 times a minute: it found the domain in the public certificate logs. The admin moved to a secret path.
- PBM Source turns new laws and regulations into compliance tasks for pharmacy benefit managers: they are found and uploaded to the dashboard automatically, with daily updates. It runs on Django, Celery, Redis and PostgreSQL and ships through GitLab CI. The hard part: every requirement is marked by line of business, so a team sees only the rules that concern it.
What it costs and who pays the bill
We review the setup, then name the work and its price: a monthly fee for an agreed list of work, or a fixed price for a one-off project such as a migration. You pay Google directly, in your own account, so the projects and the data stay yours; we review that bill with you and cut what you do not need. Every access we use is written down, so if you ever leave, the list of what to revoke is ready. More on how we price managed cloud.
When you need something else
- Google Cloud next to AWS or Azure: multi-cloud management puts every account under one set of rules; next to servers of your own, it is hybrid cloud.
- Moving onto Google Cloud, or off it: cloud migration.
- Systems that must survive the loss of a whole region: cloud disaster recovery.
- Questions and incidents handled by people who know your setup: cloud support.
Show us your Google Cloud projects: we review the setup, then name the work and its price. The rest of what we run is on managed cloud services.
