System Requirements

Hardware

The capacity is defined in terms of RPS or Requests per second.

A single transaction may require 4 requests on average, and hence 40 RPS will approximately equal to a capacity of 10 transactions per second (TPS) and 25 million transactions per month.

However, the RPS to TPS ratio might vary based on various factors such as type of integration between merchant app and hyperswitch and variability in transaction patterns. It is recommended to provision for the peak TPS capacity expected from the users.

The production configuration recommended for 40 RPS capacity is as follows (excluding monitoring services).

Baseline Requirements for 40 RPS -

HARDWARE REQUIREMENTS (40 RPS)
Kubernetes Cluster	Compute: 4 CPU cores Memory: 16GB RAM Nodes: 2 (Min) Processor: Intel Xeon Platinum 8124M or equivalent (e.g., any modern multi-core x86_64 processor with similar performance capabilities)
Database Server	Compute: 2 CPU cores Read: 8GB RAM Storage: 1TB
Redis Cache	Compute: 1 CPU core Read: 4GB RAM

Note: For enterprise deployments, scaling without a buffer is not recommended. The following additional capacity should be provisioned:

• 30–50% headroom for traffic spikes and retries

• N+1 redundancy for node-level failures

• Additional margin for rolling deployments

• Autoscaling thresholds set below maximum utilization

For planning purposes, a 40% buffer for the application layer and 50% buffer for stateful components (Database and Redis) is recommended.

Detailed guidance for scaling Hyperswitch for enterprise payment systems can be found in the Scale & Reliability section.

Software

Due to necessary time and cost considerations, only the Hyperswitch build compatible with specific operating systems, relational SQL and no-SQL databases has gone through the stringent PCI Software Security Standards (SSS) validation process.

It is strongly recommended to use the following software to ensure easy external validation such as PCI DSS certification and achieve the required performance from the installation.

Operating system

Linux version Ubuntu is 24.04 LTS is recommended.

Database

PostgreSQL version 14.x is recommended for persistent storage.

Redis version 7.x is recommended for caching

Versioning

The hyperswitch-suite is a singular reference repository to be followed for application updates. This is to ensure compatibility across application components. Semantic versioning is followed across all application components.

The approved and listed software version appears as "Hyperswitch, Version: 1.x" on the PCI SSC List of Validated Payment Software, with the major version clearly indicated. Major version components only change when there are significant feature changes, or the changes impact any part of a security standard.

The stable releases are announced on a monthly basis on the Releases page. This will include notes on each application component which includes

• New features

• Bug fixes

• Database migrations

• Breaking changes (if any)

A Continuous deployment engine automatically updates the nightly releases on a daily/ weekly basis. The nightly releases are developer builds which are not officially tested, nor deployed for production use (alpha).

Note: It is strongly recommended to not use the nightly releases in the production environment.

Devops software

Installing and managing Hyperswitch requires a good operational expertise on Kubernetes, Helm and Kubectl.

The minimum recommended versions for the devops software as follows:

• Kubernetes v1.22+

• Helm v3+

• Kubectl v1.28+