The chat can't change anything
The assistant's write commands are blocked. When it finds a fix, you get a button with the exact command on it, not a change that already happened.
SECURITY
You stay in control.
Giving any tool access to your cluster is a real decision, so here's exactly how Rigel works. It runs on your own Mac, it asks before it changes anything, and it never reports back to us.
APPROVAL
Nothing changes without your say-so.
Rigel can dig through your cluster and suggest fixes, but it doesn't make the change itself. It hands you the exact command and waits for you to click.
You confirm every change
Anything that touches the cluster shows you the exact command and waits for you to say yes.
Reading and writing are separate
Live cluster data comes in over a read-only stream. Changes go through a different, guarded path that only you trigger.
RUNS LOCALLY
It runs on your Mac, nowhere else.
Rigel isn't a server you have to stand up and protect. It's an app on your machine that talks to your clusters directly, so there's nothing exposed to the internet.
Runs on your Mac
It's an app on your machine, not a server. Nothing listens on the network, so there's no public surface to attack.
Connects out, never in
Rigel reaches your clusters from your Mac using the kubeconfig you already have. There's no Rigel server in the middle to lock down.
It can only do what you can
Rigel acts as you. If your kubeconfig and your cluster's RBAC don't allow something, neither does Rigel.
Scoped to what you're touching
Pick a namespace and the whole app narrows to it. Your cluster's RBAC still applies on top of that.
YOUR DATA
Your data doesn't go anywhere.
Rigel runs on your Mac. The only thing that ever leaves is what you choose to send to the AI, using your own key.
Local, end to end
Rigel runs on your Mac and uses your kubeconfig to reach your clusters directly. There's no Rigel server in between.
No telemetry
No analytics, no tracking, no phone-home. We don't see anything about your cluster.
Your own AI key
Chat uses an AI key you provide. That's the one place your cluster's details ever leave your machine.
Notifications you run
Alerts go out through a Signal bridge you run yourself, not a third-party paging service.
AGENT GUARDRAILS
The agent has hard limits.
The optional agent that fixes things while you're away only works inside the limits you set, and it keeps a record of everything it does.
Spend cap
A hard dollar limit on what the agent can spend on its own.
Kill-switch
Turn it off whenever you want. If it can't even read its own config, it shuts itself down rather than guess.
Namespace-scoped
It only acts in the namespaces you've put on its allowlist.
Never reads your Secrets
The agent runs inside an RBAC cage that leaves Secrets out entirely. It can't read them, so it can't leak them.
Backs up first
It snapshots a resource's YAML before changing it, so nothing it does is one-way.
Logged, with undo
Every action is recorded with a before-and-after, so you can roll it back.
COMMON QUESTIONS
Questions people ask.
- Does my cluster data leave my machine?
- It stays on your Mac and in your clusters. For chat, it goes to the AI provider you set up, using your own key. Update checks send just the image names you already run to public registries to spot new versions. Anything else, like GitOps to your own Git host, only happens if you turn it on. Nothing phones home.
- What can the AI do on its own?
- In chat, nothing that changes the cluster. Write commands are blocked, and fixes come back as buttons you approve. The optional agent can act, but only inside the spend cap, namespaces, and kill-switch you set, and it backs up and logs everything.
- Where are my credentials stored?
- Your kubeconfig stays right where it already lives on your Mac. The AI key you give Rigel is stored locally by the app. Rigel doesn't add its own encryption on top, so treat them like any other credential on your machine.
- Do I have to expose anything to the internet?
- No. Rigel is a desktop app, so there's nothing to expose. It connects out to your clusters from your Mac, and you don't open any ports or stand up a server.
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 ↗