Use cases / AWS · GCP · Azure
Use case · AWS · GCP · Azure
One operator across every cloud you run.
Checks for AWS, GCP and Azure sit alongside the Kubernetes checks, so drift is caught wherever it starts.
What it takes off your plate
01
10 groups of checks per cloud
AWS, GCP and Azure each get ten groups of checks.
02
No long-lived keys
Short-lived access, limited to each fixer.
03
One record for all clouds
The same signed, checked record, whichever cloud the problem came from.
In practice
Every fix leaves a record
Detection, cause, policy decision, fix and verification — written down, signed and exportable.
fix record · prod-eu-1VERIFIED
10:34:12DETECTCrashLoopBackOff · payments-api · OOMKilled 137
10:34:48CAUSEmemory limit 512Mi vs p99 working set 780Mi
10:35:02POLICYlimit-raise ≤ 2× · namespace payments · auto-approved
10:35:19FIXpatched limits 512Mi → 1Gi, rollout restarted
10:41:30VERIFY0 restarts, error rate 0.02%, 6 min observed
signed by workload identity · srenix-fixer@prod-eu-1
Works with what you run
Cloud
AWS · GCP · Azure
K8s distros
Kubernetes · EKS · GKE · AKS · k3s · OpenShift · RKE2
Observability & ticketing
Prometheus · Alertmanager · Grafana · Loki (paid) · OTLP (paid) · OpenProject · Jira · ServiceNow · Slack
K8s-native infra
Vault · cert-manager · CNPG · Rook/Ceph · External Secrets · Kong · ArgoCD · Cloudflare
Trigger sources
K8s informers · Alertmanager polling · Webhook (HMAC) · CronJob resync
AI providers
OpenAI · Anthropic · In-cluster vLLM
On-call should be quieter every week
Helm install in 5 minutes. No telemetry exfiltration. No per-investigation surprises.