We take the pager, your engineers keep the product work.
Monitoring, incident response and the toil that goes with running production on Google Cloud, handled by engineers who work in Terraform and fix the cause rather than the symptom. Autonomous triage on Google SecOps handles the security alert volume.
Straight to a senior GCP architect. No SDR, no slide deck.
Clients include
A good fit if
- Your product engineers are also your on-call rota, and it is costing you product work.
- You run production on Google Cloud and want it operated to agreed objectives.
- Security alerts arrive faster than anyone has time to triage them.
Probably not a fit if
- Your workloads are not on Google Cloud. We only operate Google Cloud environments.
Deliverables, not effort.
The retainer starts with your first workload in business hours. Coverage and scope grow from there on a sliding scale.
Monitoring and alerting
Alerts tied to service level objectives agreed with you, so the pager goes off for things customers notice rather than for noise.
Incident response
We respond to incidents in the covered hours, keep you informed while it is live, and write a blameless review afterwards.
Toil reduction
Recurring manual work and repeat incidents are fixed in code, usually Terraform, so they do not come back.
Patching and upgrades
Platform versions, node pools and managed service upgrades kept current on a schedule you can see.
Agentic SOC
Security telemetry in Google SecOps, with autonomous triage working the alert queue and escalating what needs a person.
Monthly reliability report
Performance against objectives, incidents and their causes, what we changed, and what we recommend next.
No surprises on the way.
Onboarding is a short, fixed piece of work before we take the pager.
- Onboarding
Review the workload
We review the first workload, its alerts, runbooks and known weak spots, and agree what we will fix before and after we take it on.
- Objectives
Agree what good looks like
Service level objectives and alert routing agreed with you, so both sides know what counts as an incident.
- Go live
We take the pager
Alerts route to us in the covered hours. Your engineers stop being the first responder.
- Every month
Review and improve
A monthly review of the report, the incidents and the toil backlog, and agreement on what to fix next.
Not included
- Product feature development.
- Workloads outside Google Cloud.
- Google Cloud usage and Google SecOps licensing, billed to your account.
What we need from you
- Access to the Google Cloud projects and the repositories for the covered workload.
- A contact for escalations that need a business decision.
- Notice of planned releases that change how the workload behaves.
Questions we get asked
What does the starting retainer cover?
Your first workload, with cover in business hours, 9 to 5. Adding workloads, extending hours or adding the Agentic SOC moves you along the sliding scale, and you see the figure before anything changes.
Can we get 24/7 cover?
Yes. Extended and 24/7 cover sit further along the sliding scale. We will price it for your workloads on a call.
Do we need Google SecOps for the Agentic SOC?
Yes, the SOC runs on Google SecOps. If you do not have it yet, we can set it up as part of onboarding.
Is there a minimum term?
The term is agreed in writing before we start. Ask on the call and we will tell you plainly.
Fixed price, fixed date, before you sign.
Rapid MVP
4 weeks
A$16,000
Agent MVP
2 weeks
A$25,000
Cloud Foundations
Fixed date, set at scoping
From A$45,000
AWS or Azure Migration
Set after assessment
Funded
Prices are set in AUD; other currencies are fixed conversions as at 15 September 2026, shown for guidance, with the contracted currency confirmed before you sign.
Talk to an architect who has done this before.
Bring your current setup and the outcome you need. You will get a view on the approach, the risks and roughly what it costs.
Straight to a senior GCP architect. No SDR, no slide deck.
Not ready to talk? See how we migrated Hapana off AWS →
Or call +61 2 8359 9507 · Hello@aviato.consulting