Liferay SaaS has the capabilities needed to launch and run a wide variety of applications designed by you and maintained by Liferay. Some applications are simple and require minimal resources while others are complex and require more. This article covers the plans Liferay offers to meet the various needs of Liferay SaaS customers as well as the resources allocated to each plan.
Definitions
- MALU: Monthly Active Logged-in Users - The aggregate number of authenticated users that have visited each customer site at least once in the calendar month.
- APV: Anonymous Page Views - The aggregate number of anonymous page views across all customer sites during a subscription term.
Plan Resources
| Pro | Business | Enterprise | |
| # of Sites | 2 Sites | 15 Sites | Unlimited |
| # of Domains | 1 domain | 10 domains | 15 domains |
| Document Library Size* | 50GB | 100GB | 300GB |
| # of project workspaces | 1 | 5 | 10 |
| Response SLA | Gold | Gold | Platinum |
| Extensions Capacity* | 1 GB / 1 vCPU | 4 GB / 8 vCPU | 6 GB / 12 vCPU |
| # of Transactions** | 500 | Unlimited | |
| UAT Cloud Sandbox | Yes | Yes | Yes |
| Dev Cloud Sandbox | No | Yes | Yes |
| Dedicated Resources Available for Purchase | No | No | Yes |
| # of emails | 10,000 per month | ||
| Database Size | 50GB | ||
| # of Deployments of Client Extensions |
9,000 deployments per month (500 Client Extensions deployments per day) |
||
| MALUs |
100 MALUs(can be increased by purchasing additional packages) |
||
| APVs |
100,000 APVs(can be increased by purchasing additional packages) |
||
* Add-ons may be purchased to expand Document Library Size and Extensions Capacity.
** A “transaction” is defined as a “completed checkout in Commerce” where a purchase or order is made. Using other Commerce functionality such as product catalog does not count as a transaction.
Please be aware that the resources, such as Document Library Size, Extensions Capacity, and Database Size are shared across all environments within a customer's subscription. This means that usage is distributed among the different environments as required. Because of this, customers should consider their resource needs across all environments when selecting a subscription and plan accordingly.
Resource & Usage Monitoring
Resources can be monitored on the Project Usage page of the Customer Portal. This page shows how much of the allotted resources have been used and the maximum allotment for the current subscription.
Calculations
- When calculating MALUs, requests performed by unknown(Guest) users are excluded. Then each user will be counted once for each site they access in a calendar month.
- When calculating APVs, requests coming from Liferay Monitoring/Health Check Systems and popular Internet crawler bots are filtered out. Headless calls, External services requests and other types of bots are counted.
- MALU and APV consumption is tracked across all environments(prd, uat, dev, etc.).
- These metrics reset at the end of the current subscription period.
Additional Information
If you have questions about your plan or add-ons, please submit a ticket and Liferay Support will be happy to assist you.