Skip to content
Launching soon

A real cluster.
Not a simulation.

Klastro starts an isolated Kubernetes cluster in seconds. You do the work inside it, and your result is graded automatically.

A Klastro lab session: the instructions panel on the left, the terminal and the deployed application on the right

The technologies you actually operate during a session

Why Klastro

Nobody learns to fix a cluster by ticking boxes

An engineer picking up Kubernetes has two unsatisfying options. Quiz platforms confirm they memorised the syntax of a manifest, never that they can bring a cluster back up. Demo labs lend them a terminal for twenty minutes and grade nothing: they leave without knowing whether they got it right.

The same gap exists in hiring. A technical interview ends on an impression, or on an algorithm exercise that says nothing about diagnosing a pod that refuses to start. Teams hiring cloud-native engineers know this, and work around it with homegrown tests that are slow to write and impossible to compare between candidates.

Those are two symptoms of one hole: there is no real, disposable infrastructure that a machine can grade. Klastro is that engine. It brings up a dedicated cluster in seconds, lets someone work in it without a safety net, then reads the cluster’s actual state to establish what is done and what is not.

A disposable cluster, graded on its real state. Learning and assessing are then just two ways of looking at the same session.

The category

Quiz platforms test recall. Demo labs grade nothing.

Klastro sits at the intersection of the two: real isolated infrastructure, work that is graded automatically, and a single engine that serves both training and hiring.

Quiz platforms test recall. Demo labs grade nothing.
Real, isolated infrastructure Quiz platforms Demo labs Klastro
Real, isolated infrastructure
Automatic, reproducible grading
Live supervision
Per-session network isolation
One engine for training and hiring

From scenario to result, in three moves

Klastro handles the infrastructure. What is left is the work itself.

  1. Pick a scenario

    A catalogue of cloud-native scenarios, or your own. Each one defines its environment type, the tasks to complete, and the validation rules that grade them.

  2. Open the environment

    A dedicated cluster starts in seconds. Terminal, editor and notes open in the browser. Nothing to install locally.

  3. Collect the result

    Validation rules run against the real cluster state. Learners see their progress, hiring teams get a score they can defend.

Four formats, one engine

Choose how you work

The same real infrastructure, framed around what you are trying to do.

Guided, hints are free

Tutorials

A step-by-step path, with notes and the editor open beside the terminal. To learn something new without getting stuck.

  • Progress is saved
  • Hints cost nothing
At launch

Graded automatically

Challenges

A failure to fix, an objective to reach. Validation rules read the real cluster state and the score lands immediately.

  • Visible score
  • Attempt history
At launch

Open, no objective

Playgrounds

An empty cluster, yours. To test a change, reproduce an incident or prep a demo, without building a local environment.

  • No imposed tasks
  • Ready in seconds
At launch

For hiring teams

Enterprise Assessments

Ordered scenarios under a global timer, live supervision, a score hidden from the candidate, and an exportable report. Grading reads the real cluster state, not a quiz answer.

  • Supervised sessions, exportable report
  • Private scenarios, SSO, EU data residency

Five environments, provisioned on demand

The scenario picks the machine it needs, and you configure nothing. Four of the five give each machine its own kernel, behind hardware isolation.

Scroll sideways

  • vcluster

    Virtual cluster

    A full Kubernetes API server per session, running as pods on the host cluster. Fastest to start and the cheapest to run. One node.

    Shares the host kernel

  • k3s-single

    Kubernetes (k3s, one node)

    A complete k3s cluster on one hardware-isolated microVM, ready in about fifteen seconds. For labs where Kubernetes is the backdrop rather than the subject.

    Own kernel, hardware-isolated

  • k3s-cluster

    Kubernetes (k3s, two nodes)

    A k3s server and one agent, each a hardware-isolated microVM. A second kubelet to schedule onto, drain, or lose.

    Own kernel, hardware-isolated

  • kubeadm-single

    Kubernetes (kubeadm, one node)

    A real kubeadm cluster on one hardware-isolated microVM, with root on the node and the control plane untainted. For static Pods, etcd, the kubelet and certificates.

    Own kernel, hardware-isolated

  • kubeadm-cluster

    Kubernetes (kubeadm, two nodes)

    A kubeadm control plane and one worker, each a hardware-isolated microVM on its own kernel. For real failure domains: draining a node, a join that will not complete, a workload that has to move.

    Own kernel, hardware-isolated

Pricing

Three self-serve plans, and a contract for enterprises

A real lab burns real resources. Lab time is metered in credits, and no overage is ever invoiced.

Community

Free

10 credits, granted once

Enough to touch real infrastructure and find out whether the format suits you.

  • Tutorials, challenges and playgrounds
  • Community scenarios from the catalogue
  • Welcome credits go to the founder once and are never renewed
  • Invited members start with no credits
Notify me at launch

Pro

€25 per seat, per month

or €250 per seat per year, which is two months free

60 credits per seat, per month

The full catalogue, for every member holding a seat.

  • Everything in Community
  • Every community and Pro scenario
  • Seats your admins assign and reassign across the team
  • Credits reset to the grant each month; unused credits do not roll over
Notify me at launch

Instructor

€50 per seat, per month

or €500 per seat per year, which is two months free

100 credits per seat, per month

Everything in Pro, plus what it takes to author scenarios and run sessions.

  • Everything in Pro
  • Scenario Studio: author, preview and publish your own scenarios
  • Instructor-led cohorts, built from reusable tracks
  • 3 cohort places included per cohort
  • Give credits from your personal balance
Notify me at launch

On every plan

  • Labs draw 1 to 6 credits an hour, depending on the environment
  • Starting a lab needs one hour of its credits in your balance
  • Labs pause when credits run out. Paused time is not charged, and no overage is invoiced
  • One running lab per scenario for each member
  • Any member can redeem a credit voucher

Enterprise Assessments

Custom

A contract, set up with our team rather than bought online. It is the only offering that opens proctored hiring assessments.

  • Proctored assessments, with scoring and reports only your recruiters see
  • Graded by validation rules against real cluster state, reproducible task by task
  • Every scenario for every member, with no seats to assign
  • Scenario Studio, SSO and private scenarios
  • Concurrent lab capacity agreed in your contract
  • Per-session network isolation, data hosted in the EU

These are the product’s prices. The service is not open yet, so nothing can be bought online today.

Enterprise Assessments

See the platform on a real hiring case

A walkthrough with the team: an assessment scenario opened in front of you, live supervision, and the report a recruiter receives. Pick a slot.

The calendar is provided by Cal.com. It loads only once you click, and nothing reaches that third party before then.

Calendar not showing? Open the booking page on cal.com

Common questions

What people ask us before we open.

When does Klastro open?
In waves, and without announcing a date we could not hold. The engine already starts clusters; what is left is the launch catalogue and account handling. People who request early access come in first.
What happens if I request early access?
You email us and we reply. No form, no tracker, no mailing list: mostly we want to know what you are trying to do, because that decides the order in which we finish the scenarios.
What exactly is a credit?
A credit is lab time. The hourly cost depends on the environment: a vcluster burns less than a two-node kubeadm cluster, because it uses fewer resources. Your balance will be visible at all times in the dashboard.
Do I need to install anything?
No. The terminal, the editor and the instructions all open in the browser. You need a connection and nothing else.
Where will my data be hosted?
In the European Union. Session clusters, the database and the backups all stay in the EU, and every session gets its own isolated network space.
Is this suitable for CKA, CKAD or CKS prep?
That is one of our launch goals. Scenarios run on real clusters and are graded against actual cluster state, the way a practical exam works, and timed challenges reproduce the time pressure. Klastro prepares you for those exams; it is not affiliated with or endorsed by the Linux Foundation.

Early access

Open the first cluster with us

We are opening in waves, starting with the people who tell us what they want to do in there. Tell us in one line which side you are on.

or write to us directly at hello@edixos.com

An email that lands in a real inbox. We answer every one.