Cloud platform for universities — research computing, AI/ML labs, and cloud-native teaching

Open-source Cozystack (CNCF project, created by Ænix) → Ænix Public Cloud, Private Cloud and AI Platform → Ænix builds, operates and migrates them.

Cozystack is an open-source cloud platform that universities and research institutions use to serve three overlapping missions on one foundation: research computing (including GPU clusters for AI/ML), reproducible research environments for publication, and curriculum delivery for cloud-native courses. It is multi-tenant via a Tenant CRD, so departments, labs, and student cohorts get isolated quotas, RBAC, and audit trails; it runs VMs and containers side by side on one Kubernetes API through KubeVirt; and it supports air-gapped deployment where research-data sovereignty matters. Ænix, which created Cozystack and co-maintains it with maintainers from other companies, builds and supports these platforms for universities, research institutes, and R&D organizations across the EU, DACH, and Central Asia, with phased engagements aligned to grant cycles.

Quick facts

  • What it is An open-source, multi-tenant Cozystack cloud platform for university research computing, reproducible research, and cloud-native teaching, built and supported by Ænix.
  • Licence Apache 2.0 (no per-CPU / per-core licensing)
  • Status Cozystack is a CNCF project (Sandbox since 2025-02-28; Incubating application in due diligence)
  • Who it is for Universities, research institutes, and R&D organizations across the EU, DACH, and Central Asia.
  • Key capability GPU-as-a-service for NVIDIA data-centre GPUs via the NVIDIA GPU Operator (passthrough of whole GPUs to VMs, NVIDIA vGPU for VMs with your NVIDIA vGPU licence, HAMi fractional sharing for pods), Tenant CRD per-lab and per-cohort isolation, KubeVirt VMs plus containers, and air-gapped support. Cozystack is accepted into the CNCF Kubernetes AI Conformance program (September 2026).
  • Standards and federation Supports reproducible-research practice (Plan S, FAIR, Horizon Europe) through declarative, versioned environments; standard Kubernetes APIs mean it can be connected to research-infrastructure services such as EOSC as a project-specific integration.
  • Engagement Phased engagement aligned to grant cycles, starting with a fixed-price 14- or 28-day Platform Readiness Assessment, and explicit capacity transfer to in-house academic IT.

Universities and research institutions in 2026 need cloud-native infrastructure for three overlapping missions: serious research computing (especially AI/ML), reproducible research environments for publication, and curriculum delivery for cloud-native courses. Cozystack provides a single open-source foundation that serves all three — multi-tenant for departments, labs, and student cohorts; KubeVirt for legacy and modern workloads; GPU-as-a-service for AI research; air-gapped support where research data sovereignty matters.

Ænix builds Cozystack-based platforms for universities, research institutes, and R&D organizations across the EU, DACH, and Central Asia.

Pairs with: Ænix Private Cloud Platform for sovereign student-data + multi-tenant research-group isolation; AI Platform for AI/ML research labs with GPU pools.


Three university missions Cozystack serves

1. Research computing infrastructure

Modern research increasingly demands GPU clusters, large-scale data processing, and HPC-adjacent workloads. AI/ML research, computational biology, climate modelling, materials science — all need infrastructure that’s between traditional HPC and modern cloud-native.

Departments, labs, cohorts
QuotasRBACAudit trails
isolated by
Cozystack Tenant CRD
Multi-tenantSelf-service
provisions
GPU-as-a-service
NVIDIA GPU OperatorHAMi fractional sharing
alongside
VMs + containers
KubeVirtOne Kubernetes API

Cozystack delivers:

  • GPU clusters for NVIDIA data-centre GPUs via the NVIDIA GPU Operator, with HAMi fractional sharing so several labs share a card rather than queue for a whole one, whole-GPU passthrough to VMs and NVIDIA vGPU for VMs with your NVIDIA vGPU licence; tenant clusters on MIG-capable cards can also use MIG partitions
  • Multi-tenant per-lab isolation — Tenant CRD model with per-lab quotas, RBAC, audit trails
  • VM and container side-by-side — accommodates legacy research workflows alongside modern containerized pipelines
  • Self-service for principal investigators — labs can provision their own environments without ticket queues
  • Reproducible environments — declarative IaC means experiments can be reproduced years later

2. Reproducible research and publication

Open science and publication-reproducibility mandates (Plan S, FAIR data principles, Horizon Europe requirements) increasingly require that research artifacts include reproducible compute environments — not just datasets and code, but the runtime that ran them.

Cozystack delivers:

  • Containerized research artifacts — research environments as Kubernetes manifests + container images
  • Air-gapped support — for sensitive research data (medical, industrial-partner)
  • Long-term archival — environments preserved alongside data for multi-decade reproducibility
  • Research data management — environments can be referenced from your RDM and DOI workflows; connecting to them is project-specific integration work
  • Federations — connecting a platform to EOSC or a national research cloud is possible through standard Kubernetes APIs, scoped per project

3. Cloud-native education and applied R&D

CS / engineering departments increasingly teach Kubernetes, KubeVirt, GitOps, observability — the modern cloud-native stack. Industrial partners running Cozystack in production benefit from graduates already familiar with the platform.

Cozystack delivers:

  • Student / cohort sandboxes — Tenant CRD per cohort, per-student quotas, automatic cleanup
  • Curriculum-ready — install/upgrade workflows that work for academic-IT teams
  • Open-source first — students can run platform on personal hardware; reproduces production reality
  • CNCF connection — Cozystack is a CNCF Sandbox project; students gain CNCF-ecosystem familiarity
  • Industrial-relevant — graduates familiar with the platform hosting providers run in production

Why universities specifically benefit from Cozystack

Beyond the three missions, several university-specific considerations:

Open-source preferred

Academic ethos, transparency, and budget constraints all favor open-source infrastructure. Apache 2.0 licence aligns with academic preferences and procurement realities.

Sovereignty for sensitive research

Medical research data and industrial-partner research with NDA constraints — all benefit from sovereign infrastructure that keeps data within institutional control. Air-gap support handles the most sensitive cases.

Federation with national / European research infrastructure

EuroHPC, EOSC, GÉANT, national research networks — because Cozystack exposes standard Kubernetes APIs, connecting a platform to these services is possible as project-specific integration work rather than a built-in feature.

Multi-stakeholder governance

Universities have complex stakeholders: principal investigators, IT departments, research-funding agencies, industrial partners, students. Cozystack’s multi-tenant model accommodates this without privileging any single stakeholder.

Long-horizon planning

Universities don’t refresh infrastructure on commercial-vendor schedules. Open-source platform with community governance fits multi-decade planning horizons.

EuroHPC and national HPC facilities adjacent

Many universities have access to EuroHPC or national HPC; Cozystack works alongside these for the workload portfolio that doesn’t need full HPC-scale.

Slurm is not the enemy, and we are not replacing it

Every research-computing conversation reaches this point, so it belongs here rather than in a footnote. Slurm is the right scheduler for tightly-coupled batch on a homogeneous cluster — MPI jobs, a fair-share queue, months of accounting history, and a user base that already knows sbatch. A Kubernetes platform does not schedule that class of work better, and a migration that takes it away buys resentment.

What the platform is for is everything the batch cluster is bad at: long-running interactive notebooks, per-group JupyterHub, web-facing research services and portals, databases behind those services, teaching environments that appear for a semester and vanish, VMs for the software a research group cannot containerize, and shared GPUs for inference rather than queued training.

Two patterns work in practice, and both are ordinary:

  • Side by side. Slurm keeps the batch partition; the platform takes the services and interactive work, with the same storage mounted on both sides so a dataset does not need copying to be used from either.
  • Slurm inside a tenant. A Slurm cluster runs as a workload on the platform — controller and nodes as VMs or containers in one tenant — so a group gets its own queue without a second physical cluster and without central IT operating it by hand.

Multi-tenancy is what makes either honest: per-group quotas on CPU, memory, storage and GPU, isolated networks, and usage attributable to a grant, which is the number a research-computing director is actually asked for.


Companies running platforms built with Ænix

Hosting providers running Ænix Public Cloud Platform in production

Hosting providers running Ænix Public Cloud Platform in production. Academic customers are not named, but the architecture is public: an academic-computing platform moved off a hyperscaler onto owned bare metal, kept one Cluster API across several clouds, and cut GPU cost roughly fivefold. AI and ML leads can start with the head of AI/ML guide. Cozystack is Apache 2.0 and installable without us, which is how most research-computing groups evaluate it before any engagement.


Engagement structure

University engagements often have specific characteristics:

  • Procurement through public-procurement portals — EU TED, member-state portals, KZ goszakup.gov.kz where applicable
  • Multi-institution consortia — engagements may serve multiple universities simultaneously
  • Capacity transfer to in-house IT — academic IT teams operate the platform after build; knowledge handover is first-class
  • Research-grant alignment — engagement timeline often aligned with grant cycles
  • Industrial-partner collaboration scope — universities increasingly partner with industry; platform supports multi-stakeholder access

For methodology see Platform Readiness Assessment.


Pricing

Cozystack platform is open source (Apache 2.0). Ænix Private Cloud Platform and AI Platform are quoted per RFP; support tiers for self-run Cozystack start at $1,250 per 10 nodes per month (see pricing). Engagement structure:

  • Phased engagement aligned with grant cycles
  • Capacity-transfer focus — engagement explicitly invests in long-term institutional capability
  • CNCF project status — Cozystack is a CNCF Sandbox project; some universities can apply open-source procurement frameworks

For specific terms see discovery call.


Ready to scope your build? Book a call →

How to start

Or read more:


Ænix created Cozystack (CNCF Sandbox project, CNCF Certified Kubernetes distribution, CNCF Kubernetes AI Conformance, OpenSSF Best Practices) and co-maintains it with maintainers from other companies. On top of it we offer three platforms — Public Cloud, Private Cloud and AI — for universities, research institutes, and R&D organizations across the EU, DACH, and Central Asia.

Frequently asked questions

Can Cozystack provide GPU access for AI/ML research labs?

Yes. GPUs are exposed through the NVIDIA GPU Operator, with HAMi providing fractional sharing so several labs can share a card instead of queueing for a whole one. Whole GPUs can also be passed through to VMs, or split between VMs with NVIDIA vGPU (requires your NVIDIA vGPU licence). On MIG-capable cards, the GPU Operator can also carve one card into hardware-separated MIG partitions for a lab’s cluster. Labs self-provision GPU environments under per-lab quotas via the Tenant CRD, without ticket queues.

How does Cozystack isolate departments, labs, and student cohorts?

Through the Tenant CRD multi-tenancy model. Each department, lab, or student cohort gets its own tenant with quotas, RBAC, and audit trails. Cohort sandboxes support per-student quotas and automatic cleanup, so teaching and research workloads stay isolated on shared hardware.

Does Cozystack support sensitive research data?

Yes. Cozystack supports air-gapped installs for medical or industrial-partner research under NDA constraints, keeping data within institutional control. This suits sovereignty requirements where research data cannot leave the institution.

Can it run both legacy VM workloads and modern containers?

Yes. Cozystack runs VMs and containers side by side on a single Kubernetes API using KubeVirt. This accommodates legacy research workflows alongside modern containerized pipelines without requiring a separate virtualization stack.

Is Cozystack suitable for teaching cloud-native courses?

Yes. Computer-science and engineering departments use it to teach Kubernetes, KubeVirt, GitOps, and observability. Because it is open source (Apache 2.0) and a CNCF project, students can run it on personal hardware and gain CNCF-ecosystem familiarity that matches production reality.

How does Ænix structure university engagements?

Ænix offers phased engagement aligned to research-grant cycles, and explicit capacity transfer so academic IT teams operate the platform after build. Engagements can run through EU TED and member-state public-procurement portals and serve multi-institution consortia.

Ready to talk?

Book a 30-minute discovery call — no commitment. We confirm fit, the right platform, and the next steps.