Any browser, or your phone
Kubepier Web opens in any browser. The kubeconfig stays encrypted in Kubepier, not copied to every team machine.
A pod in CrashLoop, a CronJob that did not run, a deployment stuck without replicas: see it and fix it from the browser or your phone, on any Kubernetes, without the machine that holds the kubeconfig.
apiVersion: v1
kind: Config
clusters:
- name: norte-prd-aks
cluster:
server: https://norte-prd-3f1c…9a2e.hcp.brazilsouth.azmk8s.io:443
certificate-authority-data: ••••••••
- name: norte-hml-aks
cluster:
server: https://norte-hml-7b20…c41d.hcp.brazilsouth.azmk8s.io:443
certificate-authority-data: ••••••••
contexts:
- name: norte-prd-aks
context: { cluster: norte-prd-aks, user: norte-ci }
- name: norte-hml-aks
context: { cluster: norte-hml-aks, user: norte-ci }
- name: norte-sso
context: { cluster: norte-prd-aks, user: norte-sso } Tokens and certificates are encrypted and never come back to the screen. 1 not supported: norte-sso uses an exec plugin (kubelogin) — connect through the Cloud account tab
OpenStep 1 of 7 Sign in with GitHub No new password to memorize: access is your GitHub account, for you and for the team.
kubectl does everything, as long as you are on the right machine, with the right context and time to type. The rest of the time, these gaps are left.
Kubepier Web opens in any browser. The kubeconfig stays encrypted in Kubepier, not copied to every team machine.
Workloads, events, usage and every cluster resource, nothing to install. The desktop app is still there, for Linux, Windows and macOS.
On Team, each person signs in with GitHub and only sees the clients granted to them. Whoever leaves the team loses access right away.
Every CronJob shows its last run and whether it is suspended, and every Job shows whether it completed, failed or is still running.
Failing pods and warning events rise to the top. On Pro, live logs, shell and restart right there.
CPU and memory per cluster, node and namespace, right in Kubepier, from the metrics-server the cluster already has.
Kubepier in the browser, for the whole team, nothing to install. Live since 2026-10-01.
The full Kubernetes IDE for Linux, Windows and macOS, based on Freelens, with what is missing in the day-to-day of running clusters.
One client on AKS, another on EKS, one on IBM Cloud and another on an on-premises cluster: all in the same catalog, with the same table and the same filters. Switching clouds is not switching tools.
The pod is Running, but the queue is clogged or the database lost a replica. Integrations link every workload to the services it uses, discovered from the pod variables, with credentials encrypted in the client settings.
The depth of every queue the pod uses, read from the container variables, and the client’s MongoDB health, right in the cluster.
Lag per consumer group and partition, messages queued and in flight, dead-letter, and which pod consumes each topic or queue.
Open connections, replicas and replication lag, slow queries, disk and memory, and which workloads use each database.
Memory used against the limit, hit rate, connected clients, keys per database and evictions.
Each integration becomes a panel inside the cluster and the client, next to the workloads, with no other tool to open.
Nobody hands a production cluster to a new tool without knowing what it does. That is why Kubepier starts read-only and makes it clear where everything lives.
Per organization, in BRL, with a 14-day free trial. Yearly plans get 2 months free.
To see the health of everything, with no risk of touching it
For those who operate clusters, not just watch
For teams serving many clients
New integrations, product news and Kubernetes tips come out first on the DevOpsRaiz YouTube and Instagram. Follow along.
Or start for free now