On-Premises Deployment Specification

This document describes the reference architecture and minimum requirements for installing and operating V5 Ultimate inside customer-controlled infrastructure. It is intentionally conservative — most deployments comfortably exceed these numbers. Final sizing for a given site is confirmed in writing during the design workshop, taking account of plant count, concurrent operator sessions, line throughput, retention period, and any HA / DR posture.

Commercial terms (licence grant, support, escrow, liability) are governed by the On-Premises Licence Addendum to the MSA. This specification is technical only and does not amend the contract.

• Bare-metal / VM (Linux)

  App + Postgres on customer-owned RHEL 9 / Ubuntu 22.04 LTS / Rocky 9. Single-host or split app/db. Suits one-site plants and validated GxP environments where IT prefers traditional package management.

• Docker / Docker Compose

  Single-host container deployment using the published OCI images and a Compose file we provide. Recommended for small/mid sites and pilot environments. Air-gap capable when run without outbound telemetry.

• Kubernetes (Helm)

  Helm chart for multi-site, HA deployments. Targets EKS / AKS / GKE / OpenShift / vanilla k8s 1.28+. Supports horizontal scaling of the app tier, externalised Postgres, and customer-managed ingress.

• Private cloud (AWS / Azure / GCP tenancy)

  Deployed inside the customer's own cloud account/VPC. Managed Postgres (RDS / Azure Database / Cloud SQL), customer KMS, customer object storage for attachments and backups. We never hold credentials.

• Hybrid (on-prem + private cloud)

  Mix on-prem and cloud tiers — e.g. app/kiosks on the plant floor with managed Postgres in the customer's cloud, or on-prem primary with a warm cloud DR standby. See the hybrid patterns section for the supported shapes.