EVERYTHING XIAOMI
Get listed
Side by side

Mirantis Kubernetes Engine vs vCluster Platform

What both publish

FactMirantis Kubernetes EnginevCluster Platform
Company headquartersMirantis lists its address as 900 E Hamilton Avenue, Suite 650, Campbell, California 95008.LinkedIn lists the headquarters at 415 Mission Street, 37th Floor, San Francisco, California 94105.
DeploymentMKE 4 supports deployment across public, private, multi-cloud, hybrid-cloud, and bare-metal environments.vCluster Cloud hosts the platform while host and virtual clusters remain in the customer's infrastructure; self-hosted deployment runs the entire platform in the customer's infrastructure.
HeadquartersCampbell, California, United StatesSan Francisco, California, United States
PurposeMKE 4 is an enterprise Kubernetes platform built on the open-source k0s distribution.vCluster Platform provides a management plane for deploying, configuring, and operating tenant cluster fleets through a web UI, CLI, and API.
SecurityMirantis describes MKE 4 as secure by default and says its default components are FIPS-validated.Enterprise features include SSO, audit logging, zero-day vulnerability alerts, security review, and FIPS-compliant images.
SupportMirantis offers a choice of 24/7 proactive support or managed services for MKE 4.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.

Mirantis Kubernetes Engine plans

  • MKE 4 subscriptionPriced on request

vCluster Platform plans

  • FreeFree
  • Open SourceFree
  • EnterprisePriced on request

Pick Mirantis Kubernetes Engine if…

MKE 4 suits organizations seeking a self-hosted Kubernetes platform across cloud and bare-metal environments. Teams should be prepared to meet its licensing, architecture, operating-system, and upgrade requirements.

Pick vCluster Platform if…

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.

Charts they share