---

Pods

A Pod is the smallest deployable unit within a Kubernetes cluster. It encapsulates a single, actively running instance of the Liferay application container.

Customers purchase a Pod count for Production. The number of active Production Pods directly determines availability: a single Production Pod provides no high availability. Multiple Pods are distributed across availability zones, ensuring that a zone-level failure does not cause downtime.

UAT (optional) always mirrors the Production Pod count and sizing. Non-Production environments are fixed at 1 Pod each. Multiple Non-Production environments may be contracted.

 

---

Standard vs. High Performance

All PaaS and SaaS customers must select a Machine Type. This choice determines the compute resources allocated to each Pod.

Pod Sizing

Environment		Standard	High Performance
Non-Production	Liferay DXP	8 vCPU / 8 GiB RAM	8 vCPU / 8 GiB RAM
Production	Liferay DXP	12 vCPU / 16 GiB RAM per Pod	16 vCPU / 24 GiB RAM per Pod
UAT	Liferay DXP	12 vCPU / 16 GiB RAM per Pod	16 vCPU / 24 GiB RAM per Pod
Autoscaling add-on	Liferay DXP	12 vCPU / 16 GiB RAM per pods (up to 10)	16 vCPU / 24 GiB RAM per pods (up to 10)

 

Quotas Included Per Environment

In each environment, depending on the Machine Type, the customer will get (per Customer Application):

Resource	Standard	High Performance
Database Storage	100 GiB	200 GiB
Database Availability	Single instance	High Availability + Data Cache
Database (UAT, PRD and DR)	2 vCPU / 16GiB RAM	4 vCPU / 32 GiB RAM
Database (non-prod only)	1 vCPU / 4GiB RAM	1 vCPU / 4GiB RAM
Search Storage	200 GiB	200 GiB
Search / LES (per Pod)**	8 vCPU / 8 GiB RAM	8 vCPU / 8 GiB RAM
Cloud Storage (doc library + backup+customizations artifacts)	1 TiB	1 TiB
Network Traffic (Monthly)	1 TiB in/out	2 TiB in/out
Logging Ingestion (Monthly)	200 GiB	1 TiB
Load Balancing	Global, 4 forwarding rules*	Global, 4 forwarding rules*

** The number of Pods of Search is dependent on the number of Production Pods of Liferay Software for which Customer has purchased and paid applicable fees. The number of Pods of Liferay Enterprise Search (LES) is dependent on the number of Pods of LES Subscription for which Customer has purchased and paid applicable fees.

The following are scoped per Customer Application, not per environment:

Resource	Standard	High Performance
NAT Gateway	3 instances, 100 GiB	3 instances, 100 GiB

 

Quota Baselines

Usage beyond these allocations is billed as overage on a per-metric basis monthly, reconciled quarterly.

Metric	Standard	High Performance
Client Extensions vCPU	3	6
Client Extensions RAM	2 GiB	4 GiB
Storage (Backup + DocLib+Customizations Artifacts)	1 TiB	1 TiB
Database Storage	100 GiB	100 GiB
Traffic / Networking	1 TiB/mo	2 TiB/mo
Logs	300 GiB	1 TiB

 

---

Limitations

Resource	Included
Build Minutes	1,000 per account / month
NAT Gateway	3 instances, 100 GiB processed (per Customer Application)

* Forwarding rules are not the same as custom domains. Multiple custom domains pointing to the same CNAME use a single forwarding rule.