# Kube-DC > Kube-DC is a managed cloud services platform for infrastructure providers and enterprise infrastructure teams. It delivers Kubernetes, databases, storage, GPU, container services, and cloud operations on Kube-DC Native, OpenStack, or VMware infrastructure. Product category: **Managed Cloud Services Platform**. Primary positioning: Bring the Hyperscaler Experience to Your Infrastructure. Supporting message: Your Infrastructure. Your Cloud. Your Customers. ## Platform - [Platform Overview](https://kube-dc.com/platform): Managed Services, Automated Operations, Infrastructure Flexibility, Commercial Operations, Interfaces, and the Kubernetes-native foundation. - [Kubernetes as a Service](https://kube-dc.com/platform/managed-kubernetes): Tenant-administered Kubernetes clusters with hosted control planes, worker pools, networking, storage, observability, and lifecycle operations. - [Namespace as a Service](https://kube-dc.com/platform/namespace-as-a-service): Isolated Kubernetes Project environments for container workloads without a separate tenant cluster. - [Database as a Service](https://kube-dc.com/platform/database-as-a-service): Managed PostgreSQL and MariaDB workflows with credentials, monitoring, high availability, and documented protection workflows. - [Storage as a Service](https://kube-dc.com/platform/storage): Persistent block storage and S3-compatible object storage with project access controls and quotas. - [GPU as a Service](https://kube-dc.com/platform/gpu-ai-cloud): Deployment-specific shared-container and dedicated-device GPU service models on qualified hardware and software profiles. - [Virtual Machines](https://kube-dc.com/platform/virtual-machines): Linux and Windows virtual machines managed as Kubernetes resources with project networking and storage. - [Cloud Networking](https://kube-dc.com/platform/networking): Project VPCs, subnets, public and floating IP workflows, load balancing, and provider network integration. - [Backup and Recovery](https://kube-dc.com/platform/backup-and-recovery): Workload-specific snapshot, backup, retention, and restore workflows for supported services. - [Observability](https://kube-dc.com/platform/observability): Integrated metrics, dashboards, logs, alerts, and platform health workflows. - [Security and Identity](https://kube-dc.com/platform/security): Organization identity realms, Project RBAC, network boundaries, secrets, certificates, and audit visibility. - [Billing, Plans and Quotas](https://kube-dc.com/platform/billing-and-quotas): Plans, Organization and Project quotas, usage controls, and supported billing workflows. - [Web UI](https://kube-dc.com/platform/web-ui): Role-aware self-service and operational views for Organizations, Projects, workloads, managed services, networking, storage, security, and quotas. - [API and Automation](https://kube-dc.com/platform/api-and-automation): Integrate portals, internal platforms, delivery pipelines, and operational workflows with the Kube-DC tenant and service model. - [kubectl Workflows](https://kube-dc.com/platform/kubectl): Governed kubeconfig and kubectl access to managed clusters and Project Kubernetes resources. - [AI Skills and Assisted Management](https://kube-dc.com/platform/ai-assisted-management): Documented AI Skills and supported coding-assistant workflows using the current user's permissions. - [WHMCS Integration](https://kube-dc.com/platform/whmcs-integration): Qualified product, ordering, customer, and lifecycle mappings between WHMCS and Kube-DC cloud services. ## Infrastructure - [Infrastructure Overview](https://kube-dc.com/infrastructure): Choose Kube-DC Native or extend a qualified OpenStack or VMware environment. - [Kube-DC Native](https://kube-dc.com/infrastructure/kube-dc-native): Turn supported bare-metal infrastructure into the fullest Kube-DC cloud experience, with VMs, Kubernetes, databases, storage, GPU, networking, operations, multi-tenancy, usage and billing in one Kubernetes-native platform. - [Kube-DC for OpenStack](https://kube-dc.com/infrastructure/openstack): Keep OpenStack for infrastructure and tenancy while adding Kube-DC managed services in a qualified environment. - [Kube-DC for VMware](https://kube-dc.com/infrastructure/vmware): Keep existing VMware infrastructure and add Kube-DC managed services, with a separate path to Kube-DC Native when replacement becomes the goal. ## Solutions - [Solutions Overview](https://kube-dc.com/solutions): Provider services, sovereign and private cloud, AI and GPU cloud, developer cloud, and VMware replacement. - [Cloud Provider Platform](https://kube-dc.com/solutions/cloud-platform): Launch a white-label cloud for VMs, Kubernetes, databases, storage and qualified GPU services. The provider remains Merchant of Record and owns the brand, pricing, customer relationship and applicable Stripe payment flow. An 80/20 revenue-share option is available for qualifying partner deployments, with final terms confirmed during onboarding. The responsibility matrix separates provider infrastructure, customers and Level 1 support from Kube-DC platform operations and Level 2/Level 3 expertise. Billing includes supported Stripe and WHMCS workflows, plans, quotas and usage controls across Kube-DC Native, qualified OpenStack and qualified VMware deployment options. - [Sovereign and Private Cloud](https://kube-dc.com/solutions/sovereign-cloud): Deliver managed services while retaining control of infrastructure, data location, networking, operations, and customer relationships. - [AI and GPU Cloud](https://kube-dc.com/solutions/gpu-ai-cloud): Turn supported GPU infrastructure into governed services for virtual machines and Kubernetes workloads. - [Developer Cloud](https://kube-dc.com/solutions/developer-cloud): Give development teams governed self-service access to containers, Kubernetes, virtual machines, databases, storage, and networking. - [VMware Replacement](https://kube-dc.com/solutions/vmware-replacement): Replace VMware with Kube-DC Native and move appropriate workloads to a complete Kubernetes-native cloud platform in phases. ## Comparisons - [Kube-DC vs VMware](https://kube-dc.com/compare/vmware) - [Kube-DC vs OpenStack](https://kube-dc.com/compare/openstack) - [Kube-DC vs OpenNebula](https://kube-dc.com/compare/opennebula) - [Kube-DC vs Red Hat OpenShift](https://kube-dc.com/compare/openshift) ## Commercial and Product Resources - [Pricing](https://kube-dc.com/pricing): Published Kube-DC Native software pricing and architecture-specific commercial scoping for qualified OpenStack, VMware, provider, and enterprise deployments. - [Resources](https://kube-dc.com/resources): Documentation, datasheet, demo, live cloud, GitHub, and product direction. - [Documentation](https://docs.kube-dc.com/) - [Datasheet v6 - Download PDF](https://kube-dc.com/manus-storage/Kube-DC-Datasheet-v6_f2cc68d6.pdf) - [Platform Datasheet](https://docs.kube-dc.com/datasheet/) - [Public GitHub Repository](https://github.com/kube-dc/kube-dc-public) - [Live Cloud](https://kube-dc.cloud/) - [Book a Demo](https://www.cal.eu/kube-dc/30m) ## Current Capability Boundaries - GPU services are available through deployment-specific, qualified hardware, kernel, driver, operator, isolation, and workload profiles. - OpenStack and VMware integrations are qualified per environment and adapted to the existing compute, storage, networking, identity, and operational architecture. - Kube-DC Native starts from three supported bare-metal nodes for production deployments. - Distributed File Storage is not presented as a released capability until implementation, documentation, and release verification are complete.