It finds the cause
Ask why something's broken and it traces it through your logs, events, and the resources nearby until it lands on the actual cause.
EVERYTHING IT DOES
Everything it does. Every layer, covered.
A plain-English AI assistant, a one-click app store, and an agent that never sleeps. Here's everything Rigel does, so you can run production Kubernetes without an ops team.
- 58
- one-click apps
- 24/7
- autonomous watch
- 0
- lines of YAML (unless you want)
- 100%
- your hardware
AI CHAT
It does the digging, you make the call.
When something breaks, you ask the chat about it. It goes digging through your logs, events, and the resources around them, then comes back with a button to fix what it found.
Fixes you approve
Every fix comes back as a button with the exact command on it. You see what it'll run before it runs.
Pull in any resource
Type @ to drop a pod, deployment, or service into the chat. Autocomplete finds it for you.
See how it got there
A side pane shows how it reasoned through the problem, not just the answer it landed on.
Bring your own model
Claude, Codex, Gemini, or OpenCode, using your own key. A fast one for a quick look, a heavier one for something gnarly.
Keeps your history
Past chats stick around, and any panel can hand what you're looking at to the chat with the context already loaded.
AUTONOMOUS AGENT
Install it, turn it on, and it watches for you.
It's opt-in. You deploy it into your cluster as its own service and switch it on. Once it's running, it watches your allowlisted namespaces and fixes what it knows how to handle, inside the limits you set. You decide how much it does on its own, and anything it's unsure about waits in a queue for you.
Limits you set
A kill switch, the namespaces it's allowed to touch, and caps on how often it can act. It never works outside them.
Knows what to look for
Crash loops, OOM kills, pods stuck pending, rollouts going sideways, a node gone NotReady. It catches them without you watching.
Asks when it's unsure
Anything it won't decide by itself goes into a Needs You queue for you to weigh in.
Opens fix PRs
When the fix belongs in code, it branches, commits, and opens a pull request on your linked GitHub repo for you to review.
Saves a copy first
It snapshots the YAML before changing anything, so nothing it does is one-way.
Undo any action
Every change goes in the log with the snapshot it took right before running, and an undo button next to it.
A record of everything
A running log of every move it's made, there whenever you want to check its work.
Sends you a digest
Schedule a plain-English cluster summary and it arrives on your phone on whatever cadence you set.
ALERTS
Tell it what to watch for.
Say what you care about in a normal sentence and Rigel turns it into a watch that actually runs. When it trips, your phone buzzes. No PromQL to learn first.
Write it like a text
“Text me if postgres goes down.” This sets up an alert to notify you when postgres breaks.
Reaches your phone
Alerts come through Signal, Matrix, Discord, Slack, or a plain webhook when something on your list breaks.
Runs in the background
Whatever you describe becomes a live watch that just keeps running.
Nothing else to run
No Prometheus, no Alertmanager, no dashboards to keep alive. Rigel does the watching itself.
APP CATALOG
Self-host the things you'd usually pay for.
Pick something from the catalog and it's running on your cluster a few minutes later. The convenience of a hosted service, without the monthly invoice.
58 apps, ready to go
Dev tools, databases, media, networking, observability, and more, all set up to deploy as they are.
Walks you through it
It asks for the namespace, hostname, and storage, with reasonable answers already filled in.
Limits already set
Each app ships with CPU and memory settings that work, so you're not guessing at numbers you don't know yet.
Flags updates
Rigel watches for new versions and tells you when an app has an upgrade waiting.
Removes everything
Done with an app? It finds every piece of it, has you type the name to confirm, and clears it all out.
On hardware you own
It all runs on your own cluster. Your data stays with you, and nothing shows up on a bill.
CLUSTERS & CONNECTIONS
Every cluster in one place.
Rigel sits in front of all of them at once. Connect the clusters you already run, or stand up a throwaway one locally, and switch between them without juggling contexts on the command line.
One console, every cluster
A rail of your clusters down the side. Click one and the whole app re-points at it. Give each a name and an icon.
Connect what you've got
Point it at EKS, GKE, AKS, or DigitalOcean, or just import a kubeconfig. It flags expired auth and tells you what permission it's missing.
Spin up a local one
Stand up a kind or k3d cluster from the app when you want somewhere to test. It cleans up after itself.
Scope to a namespace
Narrow the whole app to one namespace, or open it back up. Your cluster's RBAC still applies underneath.
DEPLOY & GITOPS
Get things onto the cluster.
Helm charts, cluster add-ons, a Git repo, a pasted manifest, or an old Compose file. However you like to ship, it's a few clicks, and every apply is one click away from being undone.
Helm releases
Browse charts, install them, and manage what's already released, without memorizing Helm's flags.
One-click add-ons
Metrics Server, Descheduler, cert-manager, and ingress-nginx install from a menu, wired up and ready.
GitOps from a repo
Connect a GitHub repo, point it at your manifests, and sync. Edit files and deploy without leaving the app.
Apply raw YAML
Paste or load a manifest and apply it, with the same confirm step as everything else.
Migrate from Compose
Hand it a docker-compose.yml and it works out the Kubernetes equivalent for you to review.
Undo a deploy
Every apply lands in a recent-deploys list with a one-click rollback of the whole batch.
THE CONSOLE
Every resource, one console.
No flipping between kubectl get and a wall of YAML. Every core Kubernetes resource gets its own panel:
searchable, namespace-scoped, and one click from a fix.
Workloads
Deployments, StatefulSets, DaemonSets, Jobs & CronJobs
Pods
Phase, restarts and live CPU / memory sparklines
Services
Ports, endpoints and type at a glance
Ingresses
Hosts, TLS and backend routing
ConfigMaps
Keys, values and sizes, searchable
Secrets
Masked values, types and sizes
Storage
PVCs, access modes and capacity
Namespaces
Create, delete and scope the whole console
Nodes
Capacity, status, cordon & drain
RBAC
Roles, bindings and service accounts
Certificates
cert-manager status and renewals
Events
A live feed of what the cluster is doing
HANDS-ON CONTROLS
For when you'd rather just do it yourself.
AI is great until you already know exactly what you want. The everyday operations are all here as buttons, so you're not typing out kubectl or editing YAML by hand for something simple.
Port-forward
Forward any service or pod to localhost. It notices when the port's already in use.
Live logs
Tail pod logs as they happen, streamed straight to you. Set how far back to start.
Scale and restart
Scale up or down, restart, pause or resume a rollout. A button for each.
Edit env and images
Change environment variables, swap a container image, or adjust requests and limits in place.
Node operations
Cordon, uncordon, and drain nodes without digging up the right flags.
CronJobs
Suspend or resume a schedule, or trigger a run right now.
CLUSTER OVERVIEW
See where everything stands.
One place to read how the cluster's doing. Hand anything that looks wrong straight to the chat to dig into.
The dashboard
Node, pod, and deployment health in one view, with an investigate button on anything that looks off.
Connectivity map
See how pods and services are talking, and where the traffic isn't healthy.
Database radar
Finds your Postgres, MySQL, and Supabase instances for you. Copy a connection string, reveal credentials, or forward a port.
Right-sizing
Points out workloads asking for too much or too little, and tells you what to set instead.
RBAC & AUDITS
Know who can do what.
Trace any account to the permissions it actually holds, catch the grants that are too broad, and run a reliability, security, or performance sweep that hands back fixes instead of a wall of findings.
See who can do what
Pick a user or service account and Rigel traces it through its bindings and roles to the exact verbs it holds.
Spot the risky grants
It scores roles and bindings so wildcards and cluster-admin-shaped access stand out before they bite you.
Grant it in place
Create roles and bindings from the panel, each shown as the exact command first, and copy access across clusters.
Audit skills on tap
Run a Reliability, Security, or Performance sweep and get findings back with one-click fixes for each.
PRIVATE BY DEFAULT
You're always in control.
Rigel can do a lot and it excels in diagnosing and suggesting fixes. Non-mutating commands run autonomously while mutating commands require your approval via raised action buttons from the chat.
The assistant does the work
If a node goes down overnight, the assistants will work together to contain the blast radius.
Runs on your machine
A local desktop app that uses your established kube config to talk directly to your cluster.
Your keys on your cluster
Your kubeconfig and credentials stay on your machine and in your clusters. Nothing is sent to us.
Namespace scoping
One shared namespace filter scopes the entire console to exactly what you want to touch.
NO BOILERPLATE
All the parts you don't have to carry.
The usual Kubernetes toolbelt stays out of your way. Rigel handles the machinery so you can describe what you want in plain English.
no YAML to hand-write no PromQL no Prometheus to run no Helm CLI no kubectl memorized no dedicated ops team
Skip the ops team.
Download Rigel and connect your first cluster in a couple of minutes. Free while in beta.
Windows and Linux All downloads ↗