OpenAna + Google Cloud

Insight into GCP resources, billing and security posture across projects.

Live connectionCloud

Ana + Google Cloud

What Ana does with it.

Read-only analysis of resources, cost and security posture, and IaC changes through your pipelines.

01
Resource and billing analysis per project
02
Security posture findings with the fix in code
03
Drift detection between Terraform and live resources

Setup

Connected in four steps.

1
Connect
Open Integrations in Ana and connect Google Cloud with a scoped token, OAuth app or service account.
2
Scope it
Start read-only and choose which projects, repositories or accounts Ana can see.
3
Set the rules
Decide which actions need approval and who approves them - Ana’s guardrails enforce it.
4
Put it to work
Ana uses Google Cloud in investigations, fixes and reports, and every action is logged.

In practice

Playbooks that use Google Cloud.

SRE / DevOps

Rightsizing cloud spend without breaking SLOs

The cloud bill keeps climbing and nobody is sure which resources are safe to shrink. Ana finds idle and oversized resources, checks them against real utilization and SLOs, and ships the changes as reviewed IaC.

Read the playbook →

SRE / DevOps

Reconciling infrastructure drift

Hot-fixes in the console and manual changes pile up until Terraform plans become scary. Ana finds every drifted resource, decides with you whether code or cloud is right, and brings them back in line.

Read the playbook →

Used by

Ana’s engineers

SRE / DevOps →Security →Private equity →

Governed

Every action, approved and logged.

Ana’s guardrails decide what it may do with Google Cloud, route sensitive actions to named approvers, and keep evidence for each decision. OpenAna is SOC 2 Type II, ISO 27001, HIPAA and GDPR compliant.

Guardrails →Trust center →

FAQ