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

Assessment

Ordered scenarios under a global timer, live supervision, a score hidden from the candidate, and an exportable report.

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

Four environments, provisioned on demand

The scenario picks the machine it needs. You configure nothing.

Scroll sideways

  • vcluster

    Virtual cluster

    A full, isolated Kubernetes cluster inside the host cluster. Fastest to start, ideal for tutorials and application-level challenges.

  • kind

    Kubernetes in a VM

    A cluster running inside a dedicated virtual machine, with full node access. For anything touching the runtime or the kubelet.

  • kubeadm

    Multi-node cluster

    Two nodes brought up with kubeadm on a dedicated virtual network. For control-plane and networking failures.

  • vm

    Bare Linux machine

    A Linux VM with no Kubernetes. For systems scenarios: systemd, networking, storage, hardening.

Pricing

A real lab burns real resources

Lab time is always metered or capped. No surprises on the invoice.

Community

Free

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

  • Public scenarios and playgrounds
  • Credits on sign-up
  • Auto-graded challenges
Notify me at launch

Pro

from €25 per user, per month

Full access to the catalogue, with credits included every month.

  • Every scenario, tutorial and challenge
  • Credits included, then metered
  • Per-member progress tracking
Notify me at launch

Assessment

A contract product, enabled per organization and set up with our team. Proctoring, SSO, private scenarios, data hosted in the EU.

Book a pilot

Indicative pricing, confirmed when the service opens.

Product status

What already runs, and what is next

Klastro is not a waiting page: the engine exists and starts clusters today. Here is where we are, unrounded.

In place

3
  • Session engine

    Four environment types started on demand, isolated per session, destroyed at the end. This is the hard part, and it works.

  • Automatic grading

    Validation rules run against real cluster state and produce a reproducible score, task by task.

  • In-browser workspace

    Terminal, instructions and editor in a single tab, with nothing installed on the machine.

In progress

3
  • Launch catalogue

    The first cloud-native scenarios: guided tutorials, graded challenges and open playgrounds, reviewed one by one before opening.

  • Accounts, credits and billing

    Sign-up, credit balance and the Pro subscription. This is what stands between the engine and a public opening.

  • Assessment for teams

    Supervised sessions, private scenarios and an exportable report. The product runs; we are setting it up with the first pilot teams.

Next

1
  • Scenario Studio

    An editor for writing your own scenarios and their validation rules without touching YAML. Not started yet.

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.