Use cases / Edge fleets
Use case · Edge fleets
Small clusters, far away, no one on call.
Edge sites rarely have an SRE nearby. SreNix runs as a small distroless binary that fixes what it is allowed to and reports the rest.
What it takes off your plate
01
Very small
A 13 MB image that needs under 100m CPU and 100 MB memory, and accepts no inbound traffic.
02
Runs on k3s
Designed for lightweight distributions as well as full clusters.
03
Works when disconnected
It decides locally. Reports are sent when the connection is back.
In practice
Every fix leaves a record
Detection, cause, policy decision, fix and verification — written down, signed and exportable.
See a real example: a stuck certificate request, cleared automatically
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.