[kfaseela]

Adds the Cozystack Incubation Due Diligence document.
Project application: #1916
PR open until October 29 for TOC and public review/comment.

[github-actions]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: angellk, kfaseela

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS [angellk, kfaseela]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tokt]

Cozystack is tackling the complexity of running your private/on-prem cloud solution in a modern way.
It absolutely deserves all the support and praise. <3

[OSPFS]

We use Cozystack as a development and testing environment, where each developer can quickly provision their own Kubernetes cluster, databases, and other services.

[batonogov]

I'm part of a small team that builds and operates platforms on top of Cozystack, and by now we've run it in
production in three quite different setups — which says a lot about how flexible the project is.

• A root cluster with nested tenant Kubernetes clusters (KaaS-style) for internal teams: per-tenant Cilium,
autoscaling node groups, LINSTOR-backed storage, managed Keycloak (realm CRDs made it easy to wire LDAP
federation with an existing FreeIPA and declarative 2FA flows), per-tenant monitoring
(VictoriaMetrics/VictoriaLogs/Grafana). We host the company VPN, WAF and edge proxies on it — real
production traffic, not a lab.
• An AI/ML platform: GPU-enabled bare-metal nodes running model inference (vLLM) and AI apps, with managed
services from the Cozystack catalog (e.g. Redis) and a fully GitOps delivery pipeline — Flux, image
automation, OCI charts.
• A single-node bare-metal Cozystack as a small multi-tenant private cloud, bootstrapped with talm — proof
that the platform scales down just as well as up.

Everything is managed declaratively (OpenTofu for the platform, Flux — which Cozystack ships with — for
everything inside). We also run VMs on the platform via KubeVirt/CDI with our own self-hosted Talos image
factory.

When we needed a small feature there, we sent a PR — got a thorough and constructive review from the
maintainers, and it was merged (cozystack/cozystack#3797). Another PR of ours is open in talm (cozystack/talm#265). That
experience alone says a lot about the health of the project.

Strong +1 for Incubation — well deserved.

[hjkbnm911]

We use Cozystack as a development and testing environment.

[ushakov-667]

The most valuable CNCF project for me.

[themoriarti]

As a Cozystack contributor, I support the project’s move to Incubation.

Our experience with Cozystack has evolved from development and testing to production use since September 2026. Over the past year, I have seen meaningful progress in the platform’s capabilities and maturity, which reinforces my confidence in its technical direction.

My contributions extend beyond Proxmox VE integration to the release process and CI/CD, including work related to SBOM generation, Cosign, security scanning, and CLOMonitor. I see these improvements as important steps toward stronger software supply-chain security, transparency, and open-source project health.

I am also working on Proxmox VE integration, and CageForge is preparing to provide server infrastructure for end-to-end testing. We see this as a practical investment in interoperability and reproducible validation across infrastructure environments.

What I value most about Cozystack is its Kubernetes-native approach, declarative operations, and use of established open-source components. I welcome the project’s continued progress toward CNCF Incubation and look forward to contributing to a more secure, interoperable, and vendor-neutral ecosystem.

[emptywee]

Seems like a very promising project!

[kingdonb]

I support Cozystack entering the incubation phase and will be there to help as we move the project from Incubation into Graduated status! (🚀)

[SerjioTT]

Great! We are using cozystack as a base for cloud service in test and production envirionmet. There is very professional maintainers board in the project, not only in code but in a communication as well. I glad to see this next phase of the project development 🚀

[angellk]

Great work @kfaseela ! Suggest adding the links to example API stability and deprecation policies.

[angellk]

Examples:

• Kubernetes - API versioning/stability and deprecation policy
• Prometheus - API stability guarantees
• Cilium - Stable API / API Reference and Upgrade guide / compatibility notes

[kfaseela]

Included these links in cozystack/community#112 raised for API stability and deprecation policy, and updated the DD to include the issue. Thanks!