System Requirements

The following is a guide on the minimum recommended setup needed to run Pyramid when installed 'natively'. This does not mean it is the recommended setup.

  • These recommendations are different for Kubernetes deployments.

Native Installations




Server OS



Host Operating System


  • Desktop PRO 10 or 11
  • Server 2012 R2 onwards
  • 64-bit only. Desktops should only used for basic testing.
  • DotNet 4.7.2 should be pre-installed to simplify all installations and prevent reboots.
  • See details below on deprecated OS's.


  • Ubuntu 18, 20, 22.04
  • Debian 10, 11
  • CentOS 7
  • RedHat 7, 8, 9
  • Oracle 7, 8, 9
  • Amazon 2, Amazon 2023
  • 64-bit only.
  • See details below on deprecated OS's.

Server Hardware

Host CPUs


Standalone Server: Min 12 cores

Production environments should provide ample CPUs to process queries. See suggestions below.


Server in a Cluster: Min 8 cores

Pulse Server: Min 4 cores

Host Memory


Standalone Server: Min 16 GB Ram

Production environments should provide ample memory to host the application, in-memory databases, as well as the needs of the operating system itself. See suggestions below.

Server in a Cluster: Min 8 GB Ram

Pulse Server: Min 6 GB Ram

Host Disk

Minimum HDD space of 4 - 8 GB

Use of very fast disks, such as SSDs, is highly recommended.




Client Browser

Any fully compliant HTML5 browser

(For example, Chrome, Edge, Opera, FireFox, Safari.)

The client browser can operate on any operating system, as long as it can connect to the web application hosted on the relevant server.

IE11 is no longer supported for use with Pyramid 2023 onwards.

Client Screen Resolution

  • Desktop: Min. 1280 x 720
  • Tablet: Most normal tablet resolutions
  • Phone: Any smart phone resolution

The desktop client must support the minimum screen size to operate effectively.

Database Repository

Repository Type

SQL Server 2012 onwards

See details below on deprecated databases.

PostgreSQL 11 onwards

See details below on deprecated databases.

Oracle 10c onwards

See details below on deprecated databases.

Database sizing

  • 8 CPU cores
  • 8 GB Ram

If the repository is not hosted on the cloud, then very fast disks, such as SSDs, are required.

Host Disk

Minimum HDD space of 2 - 4 GB

Ensure there is sufficient space to handle a growing repo database.

Upcoming Deprecations

  1. Pyramid 2023.12 is the last version that will support Windows Server 2012. Customers must move off this OS.
  2. Ubuntu 16 and 18, CentOS 7, and RedHat 7 are all coming to end of life soon. Customers should start planning to move off these OS's
  3. Pyramid 2023.12 is the last version to support PostgreSQL 11, MS SQL 2012 and Oracle 10c. Customers must move off these database versions. Note that they can still be used as analytical data sources.

For more information, see our community information.

Hardware and Environment

The right setup is heavily affected by the specifics of each deployment. There are countless variables that need to be quantified and considered. The guide to scaling Pyramid provides an in-depth review of these items. Briefly, some of these considerations include:

  • Number of concurrent users : This variable will heavily influence the number of CPU's needed to keep performance optimal.
  • Query styles and consumption: If your users typically run very large queries (5,000+ rows) and do this consistently, the underlying hardware should provide enough CPU cores to not only process such large responses, but also provide enough bandwidth for other users while such queries are being processed. Networking speed will also have an impact as more data is streamed to the end users.
  • Size of the databases and the types of technologies they operate in: In-memory databases will require lots of memory to host the relevant databases. On-disk technologies are less sensitive to memory, but will require VERY fast disk access. OLAP usually needs both, but does not require the same memory footprint or amount of disk space. Generally, In-memory and memory based OLAP engines require strong CPU's.
  • Up time and back-ups: Multi-Server deployments are best suited to ensuring the highest up-time, which in means that both the hardware strategy for the application as well as the location and performance of the server hosting the database repository is important (which remains central).