System Requirements

This guide outlines the system requirements needed to successfully deploy Surfly in your environment.

Hardware Requirements

Before starting the installation, make sure that your server meets the following hardware requirements:

Minimum Requirements

Baseline specifications for basic Surfly deployment:

• CPU: 4 cores @ 2.5 GHz
• RAM: 8 GB
• Storage: 60 GB available disk space
• Network: 100 Mbps connection

High-Traffic Deployments

For environments expecting heavy usage (100+ concurrent sessions):

• CPU: 8+ cores @ 2.5 GHz
• RAM: 16 GB or more
• Storage:
  • NVMe SSD required for optimal performance
  • 60 GB+ available space
• Network: 10 Gbps connection recommended

Note

Scaling Recommendations Consider horizontal scaling (multiple servers) rather than vertical scaling for deployments exceeding 1000+ concurrent sessions. Contact Surfly support for enterprise deployment guidance.

Software Requirements

Surfly is platform-agnostic and can be deployed on any operating system and environment that supports the following software components.

• Podman v5.4.0 or higher - Container runtime for running Surfly services
• Systemd v252 or higher - Service management and process supervision
• Redis Server 6.2.18 or higher - In-memory data store for session caching and real-time data
• PostgreSQL version 16 - Primary database for application data and configuration

Note

Platform Compatibility These software requirements are based on Red Hat Enterprise Linux 9. Surfly is designed to be compatible with RHEL 9 and related distributions (including CentOS Stream 9, AlmaLinux 9, and Rocky Linux 9), while remaining platform-agnostic and able to run on any operating system that provides the minimum versions of the required software components listed above.

Outbound Network Access

To ensure successful Surfly installation, your system must be configured with outbound HTTPS access to the following Surfly domains:

• images.surfly.com
• build-agent.surfly.com

Inbound Network Access

Surfly requires inbound access on ports 80 (HTTP) and 443 (HTTPS) for web traffic. Configure your firewall to allow these ports based on your security requirements:

Caution

Only allow public access to ports 80 and 443 if your deployment requires it. Always prefer IP whitelisting to limit exposure to trusted networks and users.