OpenAna + Kubernetes

Manifests, deployments and workloads Ana analyzes, fixes and rightsizes.

Built inInfrastructure & policy

Ana + Kubernetes

What Ana does with it.

Infrastructure-as-code, Kubernetes and policy-as-code that Ana generates, reviews and enforces.

01
Diagnoses failing pods and deployments
02
Rightsizes requests, limits and node pools from observed usage
03
Manifest changes shipped through GitOps

Setup

Connected in four steps.

1
Connect your repos and cloud
Ana reads your Kubernetes code alongside the live environment.
2
Generate or review
Describe what you need, or point Ana at existing code to review and fix.
3
See the plan
Every change comes with a diff and plan so reviewers know exactly what will happen.
4
Ship through your pipeline
Changes go through pull requests and your CI/CD, never around them.

In practice

Playbooks that use Kubernetes.

SRE / DevOps

From a 3 a.m. page to root cause and fix

An alert pages the on-call engineer. By the time they open the laptop, Ana has correlated metrics, logs, traces and recent deploys, named the likely cause, and drafted the remediation for approval.

Read the playbook →

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 →

Used by

Ana’s engineers

SRE / DevOps →

Governed

Every action, approved and logged.

Ana’s guardrails decide what it may do with Kubernetes, 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