Kyverno vs Nirmata Enterprise for Kyverno
Kyverno
kyverno.ioNirmata Enterprise for Kyverno
nirmata.comSide by side
| Figure | Kyverno | Nirmata Enterprise for Kyverno |
|---|---|---|
| Price from | Free | $1,233.33/mo |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | Yes | — |
| Web | Yes | — |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 2 | 1 |
| Spec score · Infrastructure Policy as Code Tools | 8.5 (#7) | 7.2 (#17) |
| CI integration | Official documentation provides GitHub Actions workflows for testing policies in continuous integration. | Nirmata says its nctl tool can scan Terraform configurations, Dockerfiles, and Kubernetes manifests in CI pipelines. |
| Deployment | Kyverno is installed in a Kubernetes cluster, with Helm recommended for production deployments and YAML manifests also available. | Nirmata documents deploying Enterprise Kyverno on Amazon EKS and Amazon EKS Anywhere clusters. |
| Purpose | Kyverno is a Kubernetes-native policy engine for defining and enforcing policy as code. | Nirmata Enterprise for Kyverno is an OSS-compatible, no-fork distribution of Kyverno for organizations that need a hardened and supported Kubernetes policy engine. |
| Support | The project directs users to its Kubernetes Slack channels, GitHub, and mailing list for questions and discussion. | The product includes 24/7 enterprise support with SLAs for CVEs and critical fixes. |
Plans
Nirmata Enterprise for Kyverno
- Nirmata Enterprise for Kyverno$14,800 a year
In their own words
Kyverno
Kyverno is a free, open-source policy engine for defining and enforcing policy as code in Kubernetes. Its stable policy types can validate, mutate, generate or delete resources, and verify container image signatures and attestations. The Kyverno CLI can test policies against Kubernetes resource manifests in CI before they are applied to a live cluster. Documentation describes use with Helm, YAML manifests, GitHub Actions and GitOps tools such as ArgoCD. Kyverno is installed in a Kubernetes cluster; Helm is recommended for production, and YAML manifests are also available. A standard installation requires an admission controller, while background, reports and cleanup controllers are optional. Production installations should use high availability mode. The project supports CEL-based policy types and describes applying Kubernetes-style policies outside Kubernetes as part of its mission. Its webhooks default to fail-closed, so matching requests can fail if the API server cannot reach Kyverno. The project documents Cosign signatures for images and manifests, and lists CLI binaries for Linux, macOS and Windows.
Nirmata Enterprise for Kyverno
Nirmata Enterprise for Kyverno has no write-up on Specifiction yet; its figures are above.