Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.poolside.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Introduction

Poolside on-premises allows you to deploy the Poolside platform on your own hardware. This is useful for organizations that want to keep their data on-premises, have specific security requirements, must be air-gapped, have limited internet access, or have compliance requirements that prevent them from using cloud-based solutions.
This page focuses on single-node configurations. For multi-node sizing and validation, contact your Poolside representative.

​
On-premises hardware options

Poolside offers multiple on-premises deployment options optimized for different deployment scales and workload mixes. Larger HGX-based systems are intended for enterprise-scale usage, while RTX-based workstation configurations are suitable for smaller teams and departmental deployments.
Option 1:
Customer-provided hardware (BYO)		Option 2:
Turnkey HGX rack (Dell or Supermicro)		Option 3:
Turnkey GPU workstation tower		Option 4:
Turnkey GPU workstation rack
GPU configuration8× H200 (recommended)*8× H2004× RTX 60008× RTX 6000 (5U)
DescriptionSuitable for large enterprise teamsFully integrated HGX rack solution validated by PoolsideWorkstation-based option for smaller teams and individual groupsRack-mounted workstation option for mid-sized teams
Recommended scaleLarge enterprise teamsLarge enterprise teamsSmall teams and individual groupsMid-sized teams
Operating systemUbuntu 22.04 LTS, Ubuntu 24.04 LTS, or RHEL 9.6---
CPUCustomer-provided CPU (128+ cores, 3.0 GHz or higher)2× AMD EPYC 9555 (64 cores, 3.2–4.4 GHz)Intel Xeon w9-3575X (44 cores)2× Intel Xeon 6960P (72 cores each)
GPU8× NVIDIA H200 SXM (HGX baseboard, 1128 GB total VRAM)8× NVIDIA H200 SXM (HGX baseboard, 1128 GB total VRAM)4× NVIDIA RTX 6000 Blackwell Max-Q (PCIe, 96 GB GDDR6 each)8× NVIDIA RTX 6000 Blackwell Server Edition (PCIe, 96 GB GDDR6 each)
Memory1 TB DDR5 recommended
(512 GB minimum for low-concurrency or PoC environments)		1 TB DDR5
(12× 96 GB, 4800 MT/s)		512 GB DDR5
(8× 64 GB, 4800 MT/s)		1 TB DDR5
(16× 64 GB, 4800 MT/s)
Storage1 TB NVMe (OS) + 10 TB NVMe (scratch)1.92 TB NVMe (OS) + 10 TB NVMe (scratch)2× 2 TB NVMe (OS) + 2× 4 TB NVMe (data, RAID1)2× 4 TB NVMe (OS) + 2× 13 TB NVMe (data, RAID1)
NetworkDual 10G+ ethernet, 1G IPMIDual 10G RJ45, 1G IPMI10 GbE NICDual 10 GbE NICs

​
Sizing and deployment notes

  • Customer-provided hardware (option 1) can start with 4× H200 GPUs; however, capacity must be validated based on your intended workload.
  • Scale guidance assumes mixed usage of chat, completion, and agent workloads. Laguna XS.2 delivers the highest concurrent-agent throughput on every hardware tier. Choose Laguna M.1 when agent quality matters more than raw throughput.
  • Actual capacity depends on concurrency levels, model selection, and usage patterns. For concurrent-agent capacity numbers and developer seat estimates by hardware tier, see Capacity planning.
  • Poolside validates all on-premises hardware configurations before deployment.
  • Review the official power and electrical specifications provided by the hardware vendor before deployment. Certain workstation configurations may require dedicated high-capacity circuits and specialized cooling. Confirm your hosting environment meets the required power and cooling specifications.

​
Architecture

On-premises deployments run on a single Kubernetes cluster. While you can configure multiple model replicas for increased throughput, on-premises deployments do not provide high availability against hardware failures. For multi-node sizing and validation, contact your Poolside representative. The on-premises architecture includes:
  • RKE2 Kubernetes
  • PostgreSQL database
  • S3-compatible object storage
  • Keycloak identity management (optional)
  • Container registry
  • cert-manager
  • Poolside platform
Kubernetes (RKE2), the container runtime, GPU drivers, and supporting services are installed and configured as part of the on-premises installation procedure. Architecture Diagram

​
Installation

Poolside on-premises uses a step-based Terraform deployment process:
  1. Infrastructure provisioning: Provision and configure the Kubernetes (RKE2) cluster.
  2. Access configuration: Configure cluster credentials and access required for deployment.
  3. Supporting services: Deploy the infrastructure services required by the Poolside platform.
  4. Platform deployment: Deploy the Poolside platform components.
  5. Model upload: Upload Poolside models so they are available to the platform.
Installation is performed using Terraform modules that include all providers and dependencies, supporting both online and air-gapped environments. For detailed steps, see the On-premises installation guide.

​
Operational responsibilities

For all on-premises deployments, your organization is responsible for:
  • Infrastructure resilience: Power redundancy, cooling, and physical security
  • Data protection: Backup strategies for the PostgreSQL database and object storage
  • System monitoring: Resource utilization, health checks, and alerting infrastructure
  • Network security: Firewall rules, network segmentation, and access controls
  • Network bandwidth: Sufficient bandwidth for model downloads (100 GB+) and user traffic
  • Capacity planning: Scaling decisions based on user load and model requirements
  • Disaster recovery: Business continuity planning and recovery procedures
Poolside provides the validated software stack and deployment automation. Ongoing infrastructure operations, monitoring, and data protection remain your organization’s responsibility.