Open source · Kubernetes & OpenShift

Know what will fail, when, and why, before your users do.

Ruptura runs in your cluster on top of the Prometheus you already have. It turns telemetry into clear conclusions: the failure, the time left, the evidence, and the next step.

One structured result per failure, ready for your alerts and your tools.

Threshold alerts fire too late.

A rule like "memory above 90%" says a pod is in trouble, not whether it will be killed in two minutes or never. Ruptura answers the question that matters.

Conclusions, not charts

One result per failure, with the target, the failure mode, the time left and the evidence. No new dashboard to watch.

Learns each workload

Every workload is compared with its own history and its siblings, not with a global threshold.

Honest by design

Predicted and detected failures are kept apart, and Ruptura reports the data it cannot see.

Your scope, your rules

Choose the level to watch, how deep to collect, and where results go.

Kubernetes native

One custom resource, one operator, no external database. On OpenShift, results reach the cluster Alertmanager.

Open source

Apache 2.0. Runs entirely in your cluster. Your telemetry never leaves it.

How it works

Ruptura sits on top of your existing monitoring stack. Nothing to replace.

Collect

Reads Prometheus, OTLP and the Kubernetes API.

Catalog

Maps every metric to the workload it describes.

Forecast

Forecasts each workload and spots anomalies against its own history.

Conclude

Names the failure and sends it to Alertmanager, dashboards and your tools.

Failures it names today

Predicted failures carry the time left. Detected failures report what is happening now.

Predicted

saturationMemory on course to hit its limit
release_regressionA new version leaks faster than the last
replica_divergenceOne replica leaks, its siblings stay flat
recurrent_failureFailures on a regular rhythm

Detected

oom_killedContainer killed out of memory
crash_loopRepeated restarts
startup_stuckImage pull or mount failure
replicas_unavailableMissing replicas
rollout_stuckProgress deadline passed
cpu_throttlingThrottled for 10 minutes

Full rules in the failure modes reference.

Up and running in minutes

Pick the path that fits your environment.

OpenShift & Kubernetes

oc apply -f https://raw.githubusercontent.com/\
benfradjselim/ruptura/main/install/operator.yaml

Then create a RupturaInstance. On Kubernetes, set your Prometheus URL in it.

Helm

helm install ruptura \
  oci://ghcr.io/benfradjselim/charts/ruptura \
  -n ruptura-system --create-namespace \
  --set thanos.url=<your-prometheus>

Engine only. See the README for all options.

Locally, no cluster

git clone https://github.com/\
benfradjselim/ruptura
cd ruptura
docker compose up --build

Open localhost:8081 and try it on demo workloads.

Early, and looking for early adopters

Ruptura is in active development and not yet recommended for production. Try it on a test cluster and help shape the roadmap.