Gita Cloud

Kubernetes operations, hosted for you.

We run and upgrade the platform; you connect your clusters with one command. Pick a plan for the size of your team and fleet.

Preview. Illustrative pricing. Gita Cloud plans are still being designed: prices, limits and features below are examples for evaluation, not a commercial offer.

Starter

For a small team getting its first clusters in view.

$29/ monthBilled monthly · illustrative
Start free trial
Clusters
2
Nodes
20
Members
3
History
7 days
  • Live inventory of every resource
  • Timeline of cluster events
  • Incidents and node alerts
  • Pod logs
  • Email support
Most popular

Pro

For teams that operate production clusters every day.

$149/ monthBilled monthly · illustrative
Start free trial
Clusters
10
Nodes
200
Members
25
History
30 days
  • Everything in Starter
  • Terminal and kubectl console in the browser
  • Resource actions with an audit trail per user
  • ACKs, mentions and the activity center
  • Right-sizing recommendations
  • Priority support

Enterprise

For organizations with many clusters and compliance needs.

from$799/ monthBilled monthly · illustrative
Talk to sales
Clusters
Unlimited
Nodes
Custom
Members
Unlimited
History
1 year
  • Everything in Pro
  • Single sign-on (planned)
  • Audit export and custom retention
  • 99.9% uptime SLA
  • Dedicated engineer and onboarding
Compare

Every plan, side by side.

All plans share the same product. They differ in scale, history and support.

Plan comparison, illustrative
FeatureStarterProEnterprise
Connected clusters210Unlimited
Monitored nodes20200Custom
Team members325Unlimited
History retention7 days30 days1 year
Inventory, timeline and logs
Incidents and alerts
Terminal and kubectl console
Resource actions with audit
ACKs and activity center
Right-sizing recommendations
Single sign-onPlanned
Uptime SLA99.9%
SupportEmailPriorityDedicated engineer
How it works

From sign-up to your first cluster.

  1. 01

    Create your workspace

    Sign up and name your organization. Gita runs the panel, API, worker and database for you.

  2. 02

    Connect a cluster

    Run the generated command in your cluster. The agent opens an outbound connection; no inbound port or shared kubeconfig.

  3. 03

    Operate with an audit trail

    Actions run with each person's own identity in Kubernetes and show up in the timeline and cluster audit.

Need it inside your own network?

The same product installs in your cluster with one Helm command, from public images.