Private Cloud Infrastructure¶
Enterprise-grade private cloud infrastructure with dedicated hardware, managed networking, and 24/7 monitoring.
What you get¶
- Private cloud setup — your stack runs on dedicated hardware in our facilities, not on shared VPS hypervisors
- Managed Kubernetes — optional; we operate the control plane, you deploy workloads
- Load balancing — Layer 4 + Layer 7 load balancers configured against your topology
- Auto-scaling — for workloads that need it; rules configured per workload
- Backup & DR — RPO and RTO targets agreed in your contract; off-site replication included
When to use private cloud¶
Private cloud makes sense when:
- Your workload is consistently large (VPS plans don't fit; you need 10+ machines)
- You have data-residency or compliance requirements that need dedicated hardware
- You want managed Kubernetes / load balancing / auto-scaling without operating it yourself
- You need a custom SLA above the standard 99.9%
For smaller workloads, VPS Hosting typically gives the same flexibility at lower cost.
How provisioning works¶
Private cloud is not self-service from the dashboard. The flow is:
- Initial conversation — reach out via capricorncorp.com; we discuss your topology, SLA, residency needs
- Spec document — we send a written spec covering hardware, networking, software stack, SLA, pricing
- Sign-off — you review and approve; we collect deposit
- Build — typically 7-14 business days for a standard topology; longer for custom hardware
- Handover — admin credentials, runbook, on-call contact, monitoring dashboard access
Networking¶
- Dedicated VLAN — your workload is isolated at layer 2
- BGP peering — available if you have your own AS / IP space
- Inter-region replication — between Mumbai / Bengaluru / Delhi if your contract includes DR
- Private interconnect — to Capricorncorp VPS Hosting accounts for hybrid topologies
Monitoring¶
All private-cloud customers get:
- 24/7 dashboard with infrastructure-level metrics (CPU, RAM, network, storage)
- Workload metrics when Kubernetes-managed — pod-level CPU/memory, restart counts, request latency
- Alerting — your contacts notified via email + SMS on threshold breach
- Quarterly review — usage, capacity planning, recommendations
Adding capacity¶
For accounts with auto-scale rules: capacity scales automatically within agreed bounds.
For non-auto-scale workloads: request capacity additions via your dashboard or directly to the team; turnaround is typically same-day for incremental changes, longer for new physical hardware.
Off-boarding¶
Contractual notice periods apply; data export to your control happens during the notice window. No data is retained after off-boarding completes.