Every Kubernetes cluster, one calm place.
Gita turns your clusters into a live, searchable workspace — inventory, timeline, alerts, logs and a terminal — so your team finds what broke and fixes it without living in kubectl.
Runs wherever Kubernetes runs
- Amazon EKS
- Google GKE
- Azure AKS
- Red Hat OpenShift
- Rancher
- k3s
- Bare metal
From “something is wrong” to “here's why” in minutes.
Gita collects what happens inside each cluster and lays it out so anyone on the team can follow the trail — not just the person who knows the right kubectl incantation.
A timeline of everything
Incidents, alerts, changes and Kubernetes events on one axis. Zoom into the minute it broke and see what changed right before.
Ask why, get an answer
Turn cryptic events into a plain-language explanation with the likely cause and the next step.
Logs and a shell, one click away
Stream logs from any container or open a terminal in a pod or node — straight from the browser.
Diff anything
Compare a resource across clusters and namespaces, or against its previous version.
Right-size workloads
CPU and memory recommendations from real usage — mean, max, p95 and p99.
Alerts that reach the right people
Rules for alerts, incidents, security and misconfigurations — routed by channel, schedule and grace period.
Helm apps, without the CLI
Browse charts from your repositories, install with edited values and upgrade or roll back releases.
Everything you'd reach for kubectl to do
Day-to-day operations, with permissions and capabilities you control per cluster.
- Pods, Deployments, StatefulSets, DaemonSets
- Jobs and CronJobs
- Services and Ingresses
- Volumes, claims and storage classes
- ConfigMaps and Secrets
- Cordon, uncordon and drain nodes
- Scale, restart and roll back
- Import and edit YAML with validation
- Dependency graph of any resource
- Top pods and memory issues
- Audit log of every operation
- Custom resources, discovered automatically
Connected in minutes.
A lightweight agent runs inside your cluster and talks outbound to Gita — no inbound ports, no VPN, no kubeconfig sharing.
Install the agent
Pick what the agent is allowed to do and apply the generated manifest. Private registry? Point the images to it.
Watch it light up
In seconds the cluster reports in: nodes, workloads, events and health checks start flowing to your workspace.
Bring your team
Invite people to the whole organization or to specific clusters, each with the role that fits — from viewer to owner.
Powerful for engineers. Safe for everyone else.
Give the whole team visibility without handing out cluster-admin. You decide what each person — and each cluster — is allowed to do.
Capabilities per cluster
Turn resource management, logs, terminal, Secrets and ConfigMaps on or off for each cluster.
Roles that match your org
Owner, admin, analyst, viewer and billing — scoped to the organization or to single clusters.
Two-factor, enforced
Require 2FA for everyone in the organization with a single switch.
IP allowlists
Restrict access to each cluster to the CIDR ranges you trust.
A complete audit trail
Who did what, where and when — including every field that changed.
Cloud or self-hosted
Use Gita Cloud, or run the whole platform inside your own network.
Simple pricing that grows with your clusters.
Let us host it with Gita Cloud, or install it in your own cluster with one command.
Cloud
Hosted by us, ready in minutes.
- Free trial to get started
- We run, back up and upgrade the platform
- Connect clusters with one command
- Plans by clusters, nodes and team size
- Agent updates announced in the app
Self-hosted
Run Gita inside your own network.
- Deployed on your own infrastructure
- Public images, no registry login
- Works behind HTTP proxies
- Talk directly to the team that builds Gita
Prefer to run it yourself? One command.
Install the whole platform inside your own network with Helm. Connect more clusters from the panel afterwards.
helm upgrade --install gita oci://registry.gitlab.com/gita-public/releases/charts/gita \
--version 0.1.0-beta.23-dev.23 -n gita --create-namespace --waitNeeds kubectl, Helm 3.14+ and a default StorageClass. This command opens the panel through port-forward for evaluation; the guide shows the Ingress and TLS variant.
Your cluster, your data
Panel, API, worker and an evaluation PostgreSQL run in the cluster of your current kubectl context.
Public images
No registry login and no pull secret: the chart pulls its own version of every image.
First account in a minute
No setup code: the first person to sign up in the first 15 minutes becomes the administrator.
What does the agent need access to?
Only what you allow. When you connect a cluster you choose its capabilities — managing resources, logs, terminal, ConfigMaps and Secrets can each be turned off, and you can change them later.
Do I have to open ports or share a kubeconfig?
No. The agent runs inside the cluster and connects out to Gita. If your cluster reaches the internet through a proxy, you can configure it, including authentication.
Which Kubernetes distributions are supported?
Any conformant cluster — managed services like EKS, GKE and AKS, OpenShift (with a dedicated compatibility mode), Rancher, k3s and bare metal.
Can I use images from my own registry?
Yes. Gita's images are public, so most clusters pull them directly. To use a private or mirrored registry, copy the images and override the image repositories in the Helm chart.
Do I need Metrics Server?
Most of Gita works without it. CPU and memory usage, top pods and right-sizing recommendations rely on Metrics Server being installed.
How is Gita billed?
Gita Cloud is planned as monthly plans by cluster and node; the cloud page shows the proposed Starter, Pro and Enterprise plans with illustrative prices. Self-hosted installs with one Helm command; talk to us about support and commercial terms.
Give your team the calm view of Kubernetes.
Connect your first cluster today. It takes one command and a couple of minutes.