CLOUD PROVIDER PLATFORM

Launch Managed Cloud Services Under Your Own Brand

Turn your infrastructure into a white-label cloud for Kubernetes, databases, VMs, storage and GPU - with multi-tenancy, billing, automation and platform operations built in.

Your Infrastructure. Your Cloud. Your Customers.

Your infrastructure provides servers, storage, network and GPU. Kube-DC provides the cloud platform, managed services, automation and billing. You define your cloud brand, plans and pricing for businesses, developers and enterprise customers.

One Platform. Multiple Revenue-Producing Services.

The managed service portfolio includes Kubernetes as a Service, Database as a Service, Virtual Machines, Namespace as a Service, Storage as a Service and GPU as a Service on compatible hardware. The provider chooses which services to package and sell.

You Own the Customer. You Own the Revenue.

You Are the Merchant of Record. Your customers buy cloud services from you, and your brand, pricing, invoices and commercial relationship remain under your control. Customer payments can go directly to your Stripe or billing account. Kube-DC is the technology and platform partner.

Revenue Share Available

Launch with an 80/20 revenue share and no upfront platform license fee. The partner keeps 80% of the agreed cloud-service revenue and Kube-DC receives 20% as the platform technology fee. You provide the infrastructure and collect customer payments. Final terms are agreed during onboarding. Prefer a license? Choose a per-socket software plan instead. Kube-DC does not need to own your customer payment flow.

A Clear Responsibility Split

This Responsibility Matrix makes the operating model explicit. Provider responsibility covers infrastructure, connectivity, customer acquisition, pricing, Level 1 support, billing questions and the customer commercial relationship. Kube-DC responsibility covers the software stack, deployment, configuration, platform updates, 24/7 platform monitoring, platform incident response and recovery, lifecycle operations, and Level 2 and Level 3 platform expertise.

Billing Is Already Part of the Cloud Platform.

Pay-as-you-go. Stripe supports applicable subscriptions, checkout, invoicing and payment workflows, including direct payments to the provider's Stripe account. WHMCS connects existing hosting-provider ordering, plan and customer workflows; payment collection follows the configured billing integration. Plans, quotas, usage tracking and built-in billing package services and enforce commercial cloud controls.

Your Cloud - Not a Kube-DC Reseller Portal

The white-label model keeps your logo, domain, plans, pricing, invoices and customer relationship with the provider. Customers interact with the cloud service under the provider's brand.

Partner Enablement and Cloud Operations

Partner enablement can include sales playbooks, customer pitch materials, commercial modeling and team training under the agreed onboarding scope. The operating layer includes Organizations, Projects, users and roles, multi-tenancy, VPC, secrets, observability, backups, certificates, plans, quotas, usage, billing, Stripe, WHMCS, Web UI, API, kubectl and AI Skills.

Use the Infrastructure You Already Operate

The Cloud Provider Platform business model can use Kube-DC on bare metal servers, add managed services to a qualified OpenStack environment, or add managed cloud services while keeping a qualified VMware environment.

From Infrastructure to Market

Partner onboarding validates infrastructure and the commercial model, deploys and integrates Kube-DC, then enables customer launch and support handoff. Target launch in approximately 2 weeks for a ready, qualified environment. Networking, storage, integrations and validation findings can change the timeline.

Your Infrastructure. Your Customer Data.

Tenant and Project isolation, VPC networking, users and RBAC, secrets management, customer-controlled infrastructure and deployment-specific data residency support private, sovereign and regulated infrastructure architectures.

What you need to get started.

This native deployment baseline applies to bare metal servers. OpenStack and VMware deployments are sized and integrated for the existing environment.

Cluster size: minimum 3 nodes; 5 recommended for better fault tolerance and high availability. Supported hardware: x86_64 or ARM servers, including whitebox hardware, with configuration validated during onboarding.

CPU per node: 16 or more cores. RAM per node: 64 GB or more. Storage per node: 2 x 2 TB NVMe, with RAID/mirroring specified in the deployment design.

Network per node: 10 GbE data connectivity; a separate 1 GbE management connection is supported. Operating system: Ubuntu 26.04 LTS. DNS: a wildcard record such as *.cloud.example.com pointing to the cluster ingress.

GPU hardware is optional and required for GPU services; models and sharing/passthrough modes are validated. External backup storage is optional but strongly recommended for disaster recovery.

Reserve capacity for the platform

Baseline platform overhead across the whole cluster: 10 vCPU, 60 GB RAM, and 100 GB SSD/NVMe. Reserve this capacity before allocating resources to customer workloads. Final sizing depends on the selected services and workload profile.

Network layout and backups

Plan three logical networks adapted to your data center: public network for routable IP addresses, cloud network for private addressing and outbound NAT, and node network for low-latency communication and storage replication. VLANs, addressing, routing, and redundancy are agreed during review.

Kube-DC includes VM snapshots, PostgreSQL continuous backups with point-in-time recovery, MariaDB scheduled snapshots, Kubernetes resource backup, and platform configuration backup. Hot backups use tenant storage quota. An external SAN, NAS, or S3-compatible backup target is strongly recommended. Backup destinations, retention, recovery objectives, and restore procedures are agreed during onboarding.

Partner questions, answered.

Can we use our own brand and billing? Yes. Use your logo, domain, portal, and invoices. You remain the merchant of record and collect customer payments directly. Supported billing integrations are configured during onboarding.

How does revenue sharing work? Under the 80/20 model, the partner keeps 80% and Kube-DC receives 20% of the agreed cloud-service revenue, with no upfront platform license fee. Revenue definitions, settlement terms, and service scope are documented in the partner agreement. A per-socket license is also available.

Can we keep VMware or OpenStack? Kube-DC can extend an existing VMware or OpenStack environment. Integration is designed around your compute, storage, and networking architecture. Deployment on bare metal servers is also available.

Do we need GPUs to become a partner? No. You can start with Kubernetes, containers, virtual machines, databases, and storage. Add compatible GPUs when you are ready to offer GPU services.

Turn Your Infrastructure Into a Cloud Business

Show us your infrastructure, service portfolio and commercial model and we'll map the Kube-DC deployment and partnership structure.

Explore Kube-DC