
Rafay Kubernetes Operations Platform
5.6#20 in kubernetes management platformsWebAPILinuxSelf-hosted
Visit

| Fact | Rafay Kubernetes Operations Platform | vCluster Platform |
|---|---|---|
| Headquarters | Sunnyvale, California, United States | San Francisco, California, United States |
| Integrations | Rafay says it can augment Kubernetes automation tools with fleet lifecycle automation, standardization, drift detection, isolation, and self-service workflows. | The pricing feature list names Cluster API, Terraform, Rancher, Prometheus ServiceMonitor, Metrics Server, Argo CD, Vault, cert-manager, External Secrets Operator, KubeVirt and Istio integrations. |
| Purpose | Rafay builds infrastructure orchestration and workflow automation software for self-service compute consumption by sovereign AI clouds, cloud service providers, and large enterprises. | vCluster Platform provides a management plane for deploying, configuring, and operating tenant cluster fleets through a web UI, CLI, and API. |
| Security | The management operator connects to the controller through mutually authenticated zero-trust gRPC over TLS, while RBAC controls cluster actions and audit trails record activity. | Enterprise features include SSO, audit logging, zero-day vulnerability alerts, security review, and FIPS-compliant images. |
| Support | Standard support during U.S. business hours (8 a.m. to 8 p.m. EST) is included; 24×7×365 Enterprise Support is available for an additional fee of 20% of the subscription. | Enterprise plans include enterprise support, SLAs, and custom terms; the pricing page also lists priority support, private Slack or MS Teams channels, and video support. |
The platform is aimed at sovereign AI clouds, cloud service providers, and large enterprises managing Kubernetes across cloud and on-premise environments. Its air-gapped deployment option may suit organizations that need to operate without internet software downloads after installation.
vCluster Platform suits cloud and infrastructure teams managing tenant cluster fleets across supported environments. Teams considering shared-node tenancy should account for the listed shared components.