Playground
Try the whole journey. On a real cluster.
A writable Kubernetes cluster that is yours alone, with a public domain and HTTPS ready for the first thing you deploy.
No cloud account. Nothing to install. No card to start.
- 4 GB memory, 20 GB storage
- 2 vCPU4 GB memory, 20 GB storage
- for 24 hours, no card
- €0for 24 hours, no card
- a month to keep it
- €4.99a month to keep it
- cloud accounts to connect
- 0cloud accounts to connect
How it goes
Four steps, and you are the one typing
From the first click to your own app live on its own HTTPS address.
- 01
Start it
One press in the portal, under Clusters then Add a cluster, or one command in your terminal. There is no cloud account to connect, nothing to install locally, and the free trial takes no card.
ankra cluster playground create - 02
Watch it come up
The status command shows its phase, from pending through provisioning to ready. It is ready once the Ankra agent inside it checks in. Two to four minutes is the honest range to plan around.
ankra cluster playground status <cluster-id> - 03
Find its public address
The playground gets its own domain under ankra.cc, with external-dns, cert-manager and a Let's Encrypt issuer installed on it. An Ingress you deploy gets a public hostname with an HTTPS certificate. This command prints the domain.
ankra cluster domain <cluster-id> - 04
Ship something of your own
Deploy a stack through the same pipeline your production deploys use, from the stack builder, the CLI, or by asking the AI assistant. What you learn here is not throwaway knowledge about a sandbox dialect.
ankra cluster select <playground-name> ankra stack-profiles apply <profile> --deploy
Prefer to ask rather than type? Press Cmd+J in the portal and say "deploy nginx with 2 replicas": it builds the stack and ships it through the same pipeline your production deploys would use.
Not a simulator
Everything in it is the real thing
A sandbox that fakes the interesting parts teaches you nothing about the product. This one does not fake any of them.
A real node, real pods
It is one server running k3s, a complete Kubernetes cluster, not a shared view of ours. The node reports capacity, pods schedule and restart, events land where you expect them. Nothing is stubbed for the demo.
Real TLS, real hostname
Anything you publish with an Ingress gets a public HTTPS hostname under your playground's own domain, with a certificate that actually validates, so you can point a browser or a webhook at it.
Yours alone
The cluster is writable and runs on a server of its own. Deploy things, delete things, break things. It is not a shared read-only tour with the interesting buttons disabled.
The same control plane
Stacks, add-ons and the AI assistant behave exactly as they do on a cluster you own, because it is the same platform driving both. Ask it to deploy something and watch the pipeline run.
The same portable output
Everything you build is standard Helm charts and Kubernetes manifests. It moves to a cluster of your own unchanged, because it was never playground dialect to begin with.
What it costs
A real environment. A clear price.
A development and evaluation cluster on one Ankra Cloud server, with storage included. Every playground starts at the same size.
| Playground | Server | Storage | Per month | Works out to |
|---|---|---|---|---|
| Free trialFree | 2 vCPU / 4 GB | 20 GB | Free | 24 hours, no card, one at a time |
| Kept playground | 2 vCPU / 4 GB | 20 GB | €4.99 | €2.50 per vCPU |
List price in EUR excluding VAT, billed by the second for as long as the playground's server exists, and never more than the monthly price in a calendar month. The size is the whole server: Kubernetes and the components Ankra installs run on it too, so your own workloads get less than that. A kept playground can move to a larger server on the Ankra Cloud price list, at that server's price. Playgrounds are for development and evaluation only, not production, and are excluded from the SLA.
The whole cluster on one server
Kubernetes, the Ankra agent, Traefik, cert-manager and external-dns run on the playground's own server, next to your workloads. You pay for that server and nothing else: there is no separate control plane on the bill.
A server that is already a cluster
A playground is billed as its Ankra Cloud server, at the price on the Ankra Cloud price list. A server on its own is not a cluster: here Kubernetes is already installed on it, and DNS and certificates are already wired up.
One line, nothing bolted on
Storage is included: 20 GB comes with the server. A hostname needs no load balancer, because an Ingress on the cluster's Traefik gets one. And a playground never counts toward your plan's worker vCPUs.
Billed by the second
A kept playground is billed by the second for as long as its server exists, and never more than the monthly price in a calendar month. It is paid from your organisation's Ankra credit. The free trial is never charged, not even when it ends.
Start, follow and remove it from wherever you already are: the portal, the CLI, or by asking your AI agent. Moving a kept playground to a larger server is done from the CLI or your AI agent, and the resize names the sizes it can move to.
ankra cluster playground plans
ankra cluster playground create
ankra cluster playground resize <cluster-id> --size <plan>Full pricing Straight answers
The things you would otherwise find out later
A cheap environment is only cheap if nothing about it surprises you.
How long does the free trial last?
24 hours from when it was started. Ankra then deletes the playground, its server and everything on it. To keep it, save a card before the 24 hours end: the same playground stays, with everything on it. One trial runs at a time, and an organisation can start three in 30 days.
What does it cost to keep one?
€4.99 a month excluding VAT, for 2 vCPU, 4 GB of memory and 20 GB of storage. It is billed by the second, never more than that in a calendar month, and paid from your organisation's Ankra credit. A kept playground stays until you remove it. An organisation has one playground at a time.
Can I resize it later?
Yes, once you keep it, with the CLI or your AI agent: the portal has no control for it. It moves to a larger Ankra Cloud server and is billed at that server's price from the change. Changing the size restarts the server, so nothing on the playground answers for a few minutes, up to 30. A free trial keeps its size.
How do I expose something?
With an Ingress on the cluster's Traefik, which gets a public hostname under your playground's own domain and an HTTPS certificate automatically.
What is not included?
Backups. Storage is on the playground's own server and is not backed up, so keep anything you cannot lose in your own repositories and registries.
Can I run production on it?
No. Playgrounds are for development and evaluation, they must not hold personal or other sensitive data, and no service levels cover them. When something outgrows that, move it to a cluster of your own; the stacks come across unchanged.
Where it goes next
Keep it, or graduate it
The playground used to be a demo you were expected to leave. Now it is also somewhere to stay.
A kept playground is a development cluster that stays until you remove it, at 2 vCPU and 4 GB to start. When that is not enough for what you build on it, it can move to a larger server: the server restarts on the new size, so plan for a few minutes when nothing on it answers.
When something outgrows development and evaluation, the next step is a cluster of your own: import one you already run, or have Ankra build one on your account with a provider you choose. The stacks you wrote in the playground move across as they are: they are standard Helm charts and Kubernetes manifests, and they were never playground dialect to begin with.
Your next chapter
You built it. Let’s get it live.
Give your application a path to production. Give your team a simpler way to run it.
First 30 vCPU of platform usage included. Try it without a card; a card unlocks full access and €59 of credit.
From something you built to something people use.
- Deploy from your repository
- Run on infrastructure you choose
- Operate with your team and agents