The AI that fixes outages by itself — Patent pending
RRELIORASRENIX
Talk to us ↗

When something breaks, Srenix fixes it.

On its own, in minutes. It finds the cause, applies a safe fix, checks it worked, and shows exactly what it did — so no one on your team gets woken up at 3am.

Talk to us ↗ See how it works ↓
Watching
Needs attention
Fixed

Free now for early adopters · Design Partner programme

Be one of our first 100 Design Partners.

Free now for early adopters: run Srenix Enterprise on your team’s Kubernetes clusters ahead of general availability, with hands-on help and direct access to our engineers. In return, help us prove it works and shape what we build next.

Apply to be a Design Partner How the programme works

88 of 100 places left

  • Free now, while you are an early adopter
  • Early access to Srenix Enterprise
  • Hands-on help to install and run it
  • Direct access to our engineers

How it works

It never stops watching.

srenix — incident

INCIDENT

cert-manager

billing/api-tls
uses a weak 1024-bit key

raised 03:14 · nobody paged

DIAGNOSING

Srenix found the cause

  • key size 1024 bits, below policy
  • issuer and chain are healthy
  • explained by rules, no AI needed

CHECKING

Safe to apply on its own

  • Autonomy enabled
  • Breaker closed
  • Proposal present
  • Action kind allowed
  • Namespace not protected
  • Rollback present
  • Confidence ≥ 0.95

confidence 0.97 · floor 0.95

APPLYING

Reissuing the certificate

algorithm: ecdsa-p256
live state: re-checked

rollback ready before any change

RESOLVED

Fixed before anyone noticed

re-diagnosed · finding cleared
verified in 140ms

logged to the hash-chained audit trail

An animation of a live Kubernetes cluster that plays one incident in six steps, each held long enough to read: it notices a stuck certificate, explains it with plain rules first, proposes a fix with an undo, runs its seven checks, waits for an approval (or merges itself if you allowed that) and proves the fix worked. Then the next incident starts somewhere else.

By the numbers

Cautious where
it counts.

0.95confidence floor before it acts alone
7checks, in order, before any change
140msto verify the fix in the story above
0lines of your code touched to install it

Works with the stack you already run

Pricing

Start as a Design Partner.
Grow into Enterprise.

Design PartnerFree now for early adopters · our first 100 partners→ EnterpriseFlat per cluster · fleets, regulated and sovereign→

Questions

What teams ask before they install it.

Something else? Ask us — a person replies.

Who is Srenix for?

Teams that run one or more Kubernetes clusters for their organisation: platform, SRE and DevOps teams on call for production. It is not meant for individual or single-user setups.

How is Srenix different from a copilot-style SRE assistant?

A copilot helps you investigate, and then a person makes the fix. Srenix makes the fix itself, within the rules you set, and then runs the same check again to prove the problem is gone.

What happens if a fix makes things worse?

It can’t improvise: it only runs the kinds of fix you have allowed, and it re-checks every one. A fix that gets reverted later counts as a failure, and a circuit breaker stops that kind of fix running on its own again until a person looks.

Does any of our data leave the cluster?

No. Srenix runs inside your cluster and sends no telemetry out. Its optional AI features use the model endpoint you choose — host that model inside your perimeter and the prompts stay there too.

Can it change things without asking us?

Only if you let it. A fresh install finds and explains, and changes nothing. You choose which kinds of fix it may make on its own and in which namespaces; it acts alone only when all seven checks pass with confidence of at least 0.95. Everything else waits for one tap in Slack.

Can we see the source code?

Yes. Design Partners and Enterprise customers can review the source, including the whole safety envelope. It is not open source: Design Partners use it under their programme agreement, and Enterprise customers under a commercial licence.

What does it cost?

Free now for early adopters: our first Design Partners use Srenix Enterprise at no charge during the programme. After that, Enterprise is a flat price per cluster, with no fee per incident or per investigation. See pricing.

Which Kubernetes does it run on?

Any conformant Kubernetes 1.27 or newer, including EKS, GKE, AKS, k3s, RKE2 and OpenShift. It installs with one Helm chart.

Want to see it on your own cluster?

We’ll walk through a real incident on your stack, not a demo one.

Talk to us

Something just broke.

3:14 AM · nobody is awake

Srenix is on it.

Autonomous SRE