Everything Kubepier does for your clients' clusters

Catalog organized by client

Each client has a name, a color and a keyword. Kubepier uses the keyword to recognize the client from the kubeconfig context name, and you can fix a cluster’s assignment in its details drawer.

In the catalog, clusters are grouped by the owning client and can be filtered by name, client or keyword. The home screen shows one card per client with its cluster count.

Usage dashboard

CPU and memory per cluster, node and namespace, right in Kubepier, without opening Grafana.

• When the cluster has no metrics-server, the safe installer shows what will change before installing it.
• If metrics-server stops responding, the catalog tells you how long usage has been unavailable.

Filterable events

Cluster events filtered by type, namespace and reason, with warnings first. The list does not jump when the cluster updates, and the selection stays put.

Pod queues and MongoDB: RabbitMQ, Azure Service Bus and MongoDB

Kubepier reads the container environment variables, finds the queues the pod uses and shows each one with its current depth, on desktop and on the web. On the web, it also shows the client’s MongoDB health.

The RabbitMQ credentials (management URL, user and password) and the Azure Service Bus connection string live in the client settings.

Coming soon: Apache Kafka, Amazon SQS, PostgreSQL, MySQL and Redis, each with a panel inside the cluster.

AI diagnosis

Explains a CrashLoopBackOff or another failure from the pod’s events and logs, without leaving the pod screen.

You pick the provider, Claude (Anthropic) or GPT (OpenAI), and use your own API key. The key lives only while the app is open and is never written to disk.

Any Kubernetes: cloud or on-premises

• AKS (Azure Kubernetes Service), through the Azure subscription or the kubeconfig.
• EKS (Amazon EKS), through the AWS account or the kubeconfig.
• GKE, IBM Cloud, OpenShift and any managed Kubernetes, through the kubeconfig.
• On-premises, k3s, RKE, kind: if kubectl can reach the cluster, so can Kubepier.

Secure by default

• Encrypted credentials.
• Secrets shown by key only, never the values.
• No connection string ever on screen.

Kubepier Web

Kubepier in the browser and on your phone, for the whole team, nothing to install. Live since 2026-10-01 at app.kubepier.com.br.

• GitHub sign-in and organization clients.
• Clusters via kubeconfig or cloud account, with every cluster resource.
• Usage, workloads, CronJobs, Jobs, events, RabbitMQ and Azure Service Bus queues, MongoDB health, Helm releases and Custom Resources.
• Team with per-client access and a fixed egress IP to allow on the client firewall.
• On the Pro and Team plans: edit, scale and restart workloads, live logs and shell.

In three languages

The whole desktop interface in Portuguese, English and Spanish.