Summary
- Naples-based Clastix has raised €2.9 million to expand kMetal and its Kubernetes engineering and commercial teams.
- Its architecture hosts separate Kubernetes control planes on shared management infrastructure while preserving tenant isolation.
- Mistral is both an investor and customer, linking the company directly to European AI training and inference infrastructure.
Naples-based infrastructure software company Clastix has raised €2.9 million to expand a Kubernetes platform designed to let cloud operators, AI infrastructure providers, and large enterprises run more clusters without assigning dedicated control-plane hardware to each one. The seed round is the company’s first external funding and is led by CDP Venture Capital, with Mistral and Vertis also participating.
The capital will support development of kMetal, additional customer-success and solutions-engineering capacity, and commercial expansion, while Clastix will continue investing in its open-source Kamaji hosted-control-plane project. The funding amount is small beside the huge rounds associated with AI-model companies and data-centre operators, but the technical problem sits lower in the same infrastructure stack.
Training and inference environments increasingly require organisations to divide expensive computing resources between teams, customers, and workloads without reproducing an entire management layer for every cluster. Clastix is attempting to reduce that overhead while retaining separate Kubernetes environments for individual tenants.
The company’s approach matters most where operators manage their own infrastructure or large GPU fleets, because customers using a fully managed hyperscale Kubernetes service already pay a provider to absorb much of this complexity. Clastix is therefore competing for the layer beneath cloud services rather than for ordinary application developers.
Kubernetes carries its own infrastructure overhead
A conventional Kubernetes cluster has a control plane responsible for the API, scheduling, state, and controllers, which can require dedicated resources when environments are strongly separated. That overhead becomes more visible as providers create large fleets of independent clusters for customers, teams, regions, or isolated workloads.
Kamaji hosts independent control planes as workloads on shared management infrastructure rather than requiring a dedicated set of machines for every tenant. That does not mean customers simply share one undifferentiated Kubernetes cluster, because Clastix describes separate APIs, identities, state, networks, and worker environments around each tenant.
kMetal extends the approach across bare-metal infrastructure, using kernel-based virtualisation, software-defined networking, hosted control planes, storage controls, and Kubernetes-native management. The objective is to reduce duplication without removing isolation between workloads that may belong to different customers.
Shared management infrastructure creates its own engineering risks because failures, resource exhaustion, credentials, and administrative mistakes have to be prevented from spreading across tenants. Operators therefore need to understand which components remain separate and which still share a common failure domain.
AI infrastructure rewards better utilisation
Efficiency becomes particularly valuable when the underlying resource is a costly accelerator. Techopia has already examined how GPU constraints shape the economics of AI infrastructure, and better orchestration is one way providers can improve utilisation after that hardware has been acquired.
An AI infrastructure operator serving several teams or customers cannot simply place everyone inside the same environment without creating security and reliability concerns. Conversely, reproducing the full management stack for every tenant can waste capacity and increase the amount of infrastructure that has to be patched and monitored.
Hosted control planes offer a middle path in which clusters remain logically independent while the resources beneath their management layer are pooled. The value depends on whether that consolidation reduces enough cost and operational work to justify introducing another specialised platform into the infrastructure stack.
The economics become more attractive where operators already run bare metal, manage GPU pools, or provide infrastructure to third parties, because they have more reason to control the orchestration layer directly. Clastix is less likely to win customers whose main objective is to avoid managing Kubernetes altogether.
Mistral links European models to European plumbing
Mistral’s participation gives the round significance beyond its size because the French AI company is also a user of Clastix technology. Clastix says its multi-tenancy and hosted-control-plane software supports Kubernetes infrastructure for Mistral’s training and inference clusters.
The relationship illustrates a layer of European AI sovereignty that receives less attention than models or semiconductors. A locally developed model can still depend on orchestration, networking, cloud management, and infrastructure software whose ownership and availability determine whether organisations can run it on systems they control.
CDP Venture Capital is explicitly framing the investment around strengthening European infrastructure capability, although the commercial challenge remains substantial. Kubernetes is mature and competitive, while hyperscale providers already offer managed services that hide much of its complexity from customers.
Clastix therefore has to persuade infrastructure operators that additional control and efficiency justify the operational responsibility of running its stack. Mistral provides a credible production reference, but the company still has to show that the same architecture can become a repeatable product across customers rather than remaining technology valued mainly by unusually sophisticated infrastructure teams.












