Ways to use: web, phone, desktop and team
Kubepier has one account and one plan, valid in every way you use it. This page shows each one, when it is the best choice and what it cannot reach.
Web, in the browser
Kubepier Web opens at app.kubepier.com.br, in any browser, with nothing to install. You sign in with GitHub, add the clients and connect clusters through the kubeconfig or the Azure or AWS account. Credentials are encrypted in Kubepier.
- Use it when: you want to see every client from any machine, share access with the team or cannot install anything on the machine.
- Web only: Azure and AWS accounts, Bastion, the Through the cluster route for private services, team management and per-client access, the organization audit log and fixed egress IPs.
- It cannot reach: a cluster whose API does not accept Kubepier’s egress IPs, or a kubeconfig with an exec plugin (kubelogin, aws, gcloud). Use the desktop app for those.
Phone, in the browser
It is the same Kubepier Web, adapted to the phone screen. There is no app in the stores: open app.kubepier.com.br in your phone browser. For a shortcut, use the browser’s own add to home screen option.
- Use it when: you are on call, away from the laptop, and need to know whether the alert is serious.
- You can see health per client, failing pods, events, CronJobs and Jobs and the last log lines; on Pro, live logs, AI diagnosis and, for admins, restart and scale.
- For long work (editing YAML, a long shell), the desktop app or the web on a computer is more comfortable.
Desktop: Windows, macOS and Linux
Kubepier Desktop is a Kubernetes IDE built on Freelens, for Windows 10/11, macOS (Apple Silicon and Intel) and Ubuntu/Debian. It uses the kubeconfig on your machine and signs in with the same account as the web.
- Use it when: the cluster is private and you reach it over the VPN, the kubeconfig uses an exec plugin, or you prefer a full IDE.
- Desktop only: port-forward, Secure tunnel, cordon and drain, installing Helm charts and Lens Metrics (on Pro and Team, from 2.7.0), the pod Dependencies panel and presentation mode.
- Traffic goes from your machine straight to the cluster. A confirmed Pro or Team licence works for up to 7 days offline.
- It does not have: team management or per-client access (from 2.7.0, the account role applies: a Team organization member only reads), the organization audit log (the desktop one stays in a file on the machine) or Azure and AWS accounts.
Team, on the Team plan
On Team, each person signs in with their own GitHub and only sees the clients granted to them. Admins change the cluster; members only read, on the web and on desktop (from 2.7.0). Invites last 7 days; whoever leaves loses web access right away and desktop access within 6 hours.
- Use it when: more than one person looks after the clusters, or different people serve different clients.
- Per-client access applies on the web. On desktop, each person uses the kubeconfig on their own machine.
Coming soon: remote shell over Tailscale
A shell into the cluster through your own tailnet, with no port open to the internet, from your phone, Linux, macOS or Windows. It is not available yet: it is in closed beta, with a waitlist, and planned for Pro and Team.
Which one to use
| Situation | Use |
|---|---|
| See every client’s health from any machine | Web |
| An alert at night, away from the laptop | Phone (web) |
| A private cluster, reachable only over the VPN | Desktop |
| A kubeconfig with kubelogin, aws or gcloud | Desktop |
| Port-forward or a tunnel to a database in the cluster | Desktop (Secure tunnel) |
| A terminal to a host only the cluster reaches | Web (Bastion) |
| Opening the client firewall to known IPs | Web (fixed egress IPs) |
| Recording the screen without exposing the client | Desktop (presentation mode) |
| Giving someone access only to their clients | Web, on Team |
The account and plan are the same everywhere: you can use the web on your phone and the desktop app on your laptop at the same time.