Connect a cluster and deploy a first Stack
Choose where to start
The first time you sign in, Ankra asks Where do you want to start? and offers four choices. Pick the one that matches what you have today. Choose where to start compares them: what each gives you, how long it takes, what it needs and what it costs.Connect my AI agent
You use Claude Code, Cursor, Codex or another MCP client. Add Ankra to it, then ask it for what you need. About a minute.
Try a playground
You have no cluster. Ankra runs one for you and puts a starter website on it. Two to four minutes, free for 24 hours, no card.
Put my app online
Your code is in a GitHub repository. Ankra builds it and gives it a live HTTPS address. A few minutes, free for 24 hours, no card.
Connect my own cluster
You already run Kubernetes. One Helm command connects it. About a minute, and a payment method is needed first.
What you can do with Ankra
Get a cluster
Connect the cluster you already run (EKS, GKE, AKS, k3s, on-prem, even minikube) with one helm command, or have Ankra build a new one on your own cloud account.
Put your app online
Pick a GitHub repository. Ankra Pipelines builds and checks it on every push, and Ankra deploys it to your clusters at an HTTPS address.
Deploy what it runs
Compose Helm charts and manifests into a Stack, visually or by asking the AI, and deploy the same Stack to every cluster that needs it.
Find out why it broke
Ask “why is this pod failing?” on any page. The AI already has the logs, events, manifests and recent deploys, and proposes a fix you approve.
Automate it
Everything in the UI is also available from the
ankra CLI, from your AI assistant over MCP, and from your CI pipelines.How it fits together
- An organisation is your team’s account: members, roles, credentials and billing.
- A cluster is any Kubernetes cluster running the lightweight Ankra agent. The agent connects out to Ankra, so it works behind firewalls and NAT.
- A Stack is what a cluster should run: add-ons (Helm charts) and manifests (your own YAML), with variables for what differs between clusters.
- An application is your own code from a GitHub repository. Ankra Pipelines builds, checks and publishes it, and Ankra deploys it to one or more clusters - see Applications.
- Git is optional. Stacks deploy straight through the agent. Connect a repository when you want every change reviewed and versioned, and edits flow both ways - see GitOps.
Start in 15 minutes
The Quickstart takes you from nothing to a running cluster, a deployed Stack and your first answer from Ankra AI. You do not need a cluster to follow it: a free playground gives you a real one in two to four minutes, free for 24 hours without a card.Open the Quickstart
One path, a visible result at every step.
Find your way around
After the first screen, Skip to Home (or Go to Home, once you have finished one of the four choices) takes you into the portal at/next.
- Home is Ask Ankra: a conversation box where you ask Ankra AI about your organisation. Below it, Needs you lists what waits on you, In your organisation lists what you already have, and Starting points lists the choices from the first screen you have not finished.
- The sidebar has three groups. Workspace holds Home, Applications, Cost and Security. Platform folds open and holds Infrastructure (where Clusters, Managed services and Cluster meshes are), Build & delivery, Integrations & alerts and Ankra AI. Settings and help holds Identity & access, Settings and Support.
- A cluster’s own menu opens when you open the cluster from Infrastructure → Clusters. It starts with pages such as Overview, Health, Metrics, Security and Settings, and keeps Stacks, Operations, Kubernetes, Kubectl access and Audit log under Technical details.
- Press ⌘ + J (Ctrl + J on Windows and Linux) on any page to open Ask Ankra.
Run your CI on your own clusters
Ankra CI runs a repository’s tests, image builds and security scans as Kubernetes Jobs on a cluster you already connected, and reports back as a check on every pull request. Get started with Ankra CI moves your first repository in about 20 minutes.Get started with Ankra CI
From GitHub Actions or GitLab CI to a green Ankra pipeline check.
Work from your own tools
The web UI, the CLI, the MCP server and the in-product AI all use the same tools and the same permissions, so anything you can do in one you can do in the others.- CLI
- AI assistants (MCP)
- CI/CD
Automating Ankra or building an agent on it? Use the MCP server or the CLI rather than driving the web UI with a browser. Both use scoped tokens, and every call lands in your organisation’s audit log.
Where to go next
Add a cluster
Import one you have, or pick a provider for a new one.
How Stacks work
The model behind everything you deploy.
AI Assistant
What the AI can see, and what it may change.
Security
What Ankra can access, and how to restrict it.
Cloud Cost
What each cluster, namespace and Stack costs.
API Reference
The REST API behind every surface.