If you run Kubernetes in production, you already know the shape of a bad night. An expired certificate nobody booked. A deploy that quietly made things worse. A crash loop that started the moment on-call changed shifts.
The incident is rarely the hard part. The hard part is the same failure coming back next month, because nothing on the team's side closed the loop.
What Srenix does
Srenix runs inside your own cluster and closes that loop for you, one problem at a time:
- 01
It notices the problem
Srenix watches your cluster and spots the failure as it starts.
- 02
It finds the cause
It works out why it failed, not just what failed.
- 03
It fixes it inside your rules
Every fix stays within the limits you set. Nothing happens outside them.
- 04
It checks the fix worked
Srenix re-checks after every fix, so "fixed" means proven, not hoped.
Every step goes to a signed, hash-chained audit trail. No telemetry leaves your cluster.
The offer: limited places, free now
Today we are opening the Design Partner programme. Places are limited. Every Design Partner gets Srenix Enterprise free, now, ahead of general availability.
- Free, with nothing to unwind. No card, no per-investigation billing.
- Every capability as it ships. You run Srenix Enterprise on your own clusters.
- Hands-on install help. We start you from a read-only snapshot.
- Direct access to our engineers. You talk to the people building it.
- A say in the roadmap. Your problems help decide what we build next.
What we ask in return
This is a partnership, not a trial. In return, partners agree to four things:
- 01
Be a reference
Let us name you as a customer, and talk to peers who ask about Srenix.
- 02
Help us prove it works
Allow a white paper about what Srenix did on your clusters. You review it before it is published.
- 03
Share what worked
Share the fix policies that worked for you, cleaned up, with names and private details removed.
- 04
Keep the sign-offs
Keep records of the sign-offs along the way.
You can leave the programme at any time.
An honest word on where we are
Srenix is in beta, with pilots in progress. Features and pricing may change before general availability. We are not claiming we have already proven this at scale. That is exactly what the Design Partner programme is for: you run it on your clusters, with your failures, and we prove it together.
Is it a fit for your team?
You are a good fit if you:
- Run one or more Kubernetes clusters, on any cloud or on-premises.
- Have a platform, SRE or DevOps team that is on call for them.
- Have problems that keep coming back.
- Can let us try fixes inside safe limits.
- Are happy to be a reference.
Srenix is built for teams running clusters for their organisation. It is not meant for individual or single-user setups.
Three ways to start small
- 01
Apply in about five minutes
Fill in the short application form.
- 02
See it on a snapshot first
Rather see something before you commit anything? Ask us for a read-only snapshot run. Point Srenix at a directory of cluster state and it diagnoses it, with no install and no RBAC.
- 03
Thirty minutes with an engineer
Take the standing offer: an engineer runs Srenix against a failure you choose, on your own stack.
srenix diagnose --snapshot <dir>Where it runs
- Kubernetes 1.27 and newer: EKS, GKE, AKS, k3s, RKE2 and OpenShift.
- One Helm chart installs it.
- Your choice of model: any OpenAI-compatible endpoint, including an in-cluster vLLM.
Apply now
Places are limited, and the programme closes as soon as every place is taken. Apply to be one of our first Design Partners. It takes about five minutes.
Questions first? Talk to us. A person replies.