KUBE-DC PARTNER PROGRAM
Your infrastructure. Your brand. More cloud services.
Offer Kubernetes, databases, virtual machines, storage, and GPU services under your own brand. You bring the infrastructure and customer relationships. We deploy and operate the Kube-DC platform through a revenue-share partnership.
Build a broader cloud business.
Sell more services: Kubernetes, databases, virtual machines, storage, and GPU from one platform. Keep your brand and customers, give customers self-service through the portal, API and kubectl, reduce platform operations work, use your existing infrastructure, and deliver from an agreed location.
One platform. More services.
Choose the services that fit your market and available infrastructure. GPU offerings require compatible GPU hardware.
- Managed Kubernetes
- Containers / Namespace as a Service
- Virtual Machines
- Managed Databases
- GPU & AI
- Object & Block Storage
- Networking & Load Balancing
- Backups & Observability
We grow when your cloud business grows.
Our partner model is based on revenue sharing. You sell cloud services under your brand and collect customer payments directly. Kube-DC receives an agreed share of revenue from the services covered by our partnership.
You own the commercial relationship: your customers contract with you. You set their prices, issue invoices, and receive payments through your own payment setup.
We share in service revenue: Kube-DC invoices you for the agreed technology and platform operations share. The commercial terms are agreed directly with each partner.
Start without an upfront platform license fee: standard platform deployment is included in partner onboarding. You provide and fund the infrastructure, connectivity, and customer-facing operations.
You remain the merchant of record. Revenue definitions, settlement terms, and service scope are set out in the partner agreement.
Clear responsibilities. One operating model.
You operate the infrastructure and customer relationship. Kube-DC operates the platform. Each team has a clear role when it comes to delivery, support, and incidents.
Partner owns infrastructure and customers: the physical environment, commercial relationship, and first line of customer support. Kube-DC owns platform and technical operations: deployment, lifecycle, monitoring, and escalated platform support.
Data center and hardware: Partner provides facilities, power, cooling, physical security, servers, GPUs, and hardware maintenance. Kube-DC validates the platform design.
Network and connectivity: Partner provides Internet connectivity, external routing, and physical network infrastructure. Kube-DC configures and operates platform networking.
Platform software: Partner provides agreed infrastructure and access. Kube-DC deploys and manages the cloud stack, updates, maintenance, and agreed software licensing.
Sales, pricing, and billing: Partner acquires customers, sets commercial terms, issues invoices, and collects payments. Kube-DC configures supported billing integrations and provides enablement.
Customer support: Partner handles first contact, billing, usage, and initial intake. Kube-DC provides L2/L3 technical support for escalated platform issues.
Monitoring and incidents: Partner resolves infrastructure faults and coordinates customer communication. Kube-DC monitors the platform 24/7 and handles platform incidents.
Platform security: Partner owns physical security and customer-facing policies. Kube-DC handles platform patching, scanning, monitoring, and tenant isolation controls.
When an issue occurs: the partner handles customer communication. Kube-DC investigates platform issues and manages platform recovery. Hardware, power, and uplink failures are handled by the partner; both teams coordinate across the boundary.
Backup policies, restore procedures, access, escalation paths, and any existing VMware or OpenStack responsibilities are agreed during onboarding. Customer application management and workload migration are scoped separately. Service levels are defined in the partner agreement.
What you need to get started.
Native bare-metal deployment baseline only; 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 defined by 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.
From infrastructure review to launch.
A standard deployment is planned around a two-week onboarding process once infrastructure readiness and scope are confirmed. Timing depends on integrations and agreed scope.
Validate and deploy: review infrastructure, agree architecture, deploy core platform, storage, and networking. Brand and integrate: set up logo and domain, supported Stripe or WHMCS billing, team training and customer journey testing. Launch and operate: onboard customers with monitoring and support processes in place.
Equip your team to sell.
Partner onboarding includes sales playbooks, objection-handling guidance, a brandable customer presentation, and tools to model service economics. The team gets practical positioning and sales support.
Partner questions, answered.
Can we use our own brand and billing? Yes, you remain the merchant of record, use your logo, domain, portal and invoices, and collect customer payments directly.
How does revenue sharing work? Kube-DC receives an agreed share of revenue from services included in the partnership. Terms are documented in the partner agreement.
Can we keep VMware or OpenStack? Kube-DC can extend qualified existing environments; native bare-metal deployment is also available.
Do we need GPUs to become a partner? No; launch other services first and add compatible GPUs when ready.
Let's plan your cloud offering.
Share your infrastructure, target customers, and desired services. We'll map out deployment, responsibilities, and the commercial model together.