Skip to main content

When Private Infrastructure Is Required

Pooled infrastructure is intended for simple, low-resource workloads. Panther & Cub may require private or custom infrastructure before launch or later if the workload no longer fits shared operation.

Common Reasons to Use a Private Server​

  • e-commerce, customer accounts, background jobs, or application workloads;
  • more than one application or a separate database and worker stack;
  • sustained or bursty CPU, memory, disk, or bandwidth use;
  • large databases, media libraries, downloads, or log volume;
  • custom runtimes, system packages, ports, networking, or deployment processes;
  • customer requirements for resource or tenant isolation; or
  • a workload that degrades the pooled environment or exceeds its Order.

Compliance and Sensitive Data​

A private server can improve resource isolation, but it does not establish legal or regulatory compliance. The customer must identify applicable requirements and obtain appropriate legal, security, privacy, and technical advice. Encryption, logging, access controls, monitoring, backups, recovery, vendor contracts, and documentation must be scoped separately where required.

Reassessment and Migration​

Resource use and application behavior can change after launch. If a pooled workload becomes unsuitable, Panther & Cub may restrict it, require a plan change, or propose migration under the Order and Managed Hosting Service Terms. Migration work, downtime planning, and any fee will be confirmed before the move unless urgent action is permitted by the agreement to protect the service.

Contact [email protected] with the workload, current resource use, traffic pattern, and growth expectations for a sizing review.

Last updated on