Skip to content

Run your own Kubernetes without an ops team.

Rigel is an AI-assisted Kubernetes management tool. It connects to your clusters, diagnoses issues, monitors them around the clock, and applies the fixes while you sleep - delegating critical issues for your review.

rigel · cluster-prod

Cluster Overview

Deploy
CPU
42%
-6% today
Memory
61%
steady
Pods ready
8 / 8
all healthy
postgres data Running
grafana observability Running
vaultwarden apps Running
immich-server media Running
ingress-nginx kube-system Running
YOUR OPS TEAM, BUILT IN KUBERNETES AND SELF-HOSTING

K8S COMPANION

Plain-English investigations and one-click fixes you approve.

→ Rigel chat

PEACE OF MIND

Auto-remediation within your guardrails, while you sleep.

→ In-cluster agent

ALERT MONITORING

Natural-language alerts.

→ Smart alerts

SELF-HOST ENABLEMENT

One-click catalog. Self-hosted apps on your own hardware.

→ App catalog
AI CHAT

Your next Kubernetes assistant.

Connect an AI agent to track cluster health, diagnose issues, set up your self-hosted apps, and ensure smooth operation of your Kubernetes cluster.

  • Automatic investigation across logs, events & dependencies
  • Custom action buttons to increase your efficiency
Rigel 47.6°N 122.3°W

Why is checkout returning 502s?

Ingress is healthy. checkout has 2/3 replicas NotReady, and the readiness probe on :8080 is failing. Root cause: the new image points DB_HOST at a service that no longer exists.
Proposed fix 1 ACTION
kubectl set env deploy/checkout DB_HOST=postgres-primary
Approve Dismiss
AUTONOMOUS AGENT

It watches while you're away.

An in-cluster agent runs around the clock, catching drift and remediating within the guardrails you set. It helps address issues during the night to keep your apps running.

  • Your supervisor and worker team up to keep your apps running
  • Non-critical issus are handled by the assistant. Critical issues are escalated to you.
Autonomous Agent watching · 03:14 UTC
  • ingress-nginx: 502 error spike detected
  • tracing upstream: checkout pod not ready
  • auto-remediating: restarted 2 unhealthy replicas
  • error rate back to 0.00%: verified & logged
ACTIVE GUARDRAILS
spend cap $50/mo no deletes kill-switch replicas ≤ 5
SMART ALERTS

Tell it what to worry about.

Describe what matters: “text me if the postgres database goes down.” Rigel keeps watch and pings you the moment it happens.

no config no Prometheus no YAML
New alert DRAFT
text me if the postgres database goes down
PARSED
Signal postgres-primary is down

compiled to a live watch, no PromQL written

Rigel now

ALERT: postgres-primary is DOWN. I'm standing watch and already investigating the fix.

APP CATALOG

Your own private cloud.

The catalog turns “I want to self-host X” into a running app in one click, with sensible defaults and no manifests to hand-write. Host on your hardware.

Quick deploy from a 58-app catalog
No manifests to hand-write
Runs on your hardware, so your data stays yours
App Catalog 58 apps
I want to self-host nextcloud
Nextcloud
Gitea
Vaultwarden
Plausible
Immich
Postgres
Deployed · live

https://nextcloud.apps.local, live in 41s

THE FULL CONSOLE

Not just a chat box.

The AI is the headline, but underneath it Rigel is a complete Kubernetes console: every cluster, every resource, and the everyday work, all in one window.

Every cluster, one window

Switch between all your clusters from a rail down the side. Connect EKS, GKE, AKS, or DigitalOcean, import a kubeconfig, or spin up a local one.

25+ live panels

Deployments, pods, services, ingresses, config, storage, nodes, events, and more, streaming live. No refresh button.

Deploy how you like

Helm charts, one-click add-ons, GitOps from a repo, raw YAML, or an old Compose file. Every apply is one click from undo.

RBAC & audits

Trace who can do what, catch grants that are too broad, and run reliability, security, and performance sweeps that hand back fixes.

The everyday operations

Port-forward, tail logs, scale, restart, edit env and images, cordon a node. The buttons you'd otherwise type out as kubectl.

Guarded by default

Every change shows you the exact command and waits for your click. Nothing touches the cluster on its own.

Skip the ops team.

Download Rigel and connect your first cluster in a couple of minutes. Free while in beta.