SeaCat Gateway Requirements

SeaCat Gateway is prepared to be used on both virtual or physical appliances on-premise or via the cloud. TeskaLabs also provides ready-to-use cloud-based instances, containers or deployment scripts.

The sizing of a SeaCat Gateway appliance is based on the number of expected Concurrent Client Connections.

Hardware requirements

One CPU core handles ~2500 Concurrent Client Connections. Every Concurrent Client Connection consumes ~1MB of RAM.

Recommended hardware configuration:

  • 64-bit Intel/AMD CPU
  • 2GB RAM per CPU core
  • 50GB of HDD space for logging purpose (SSD is not required)
    • 1GB of additional free space for ~55.000 Client Certificates
    • 5 inodes per Client Certificate

SeaCat Gateway allows use of RSA hardware acceleration cards such as AHA604 or AHA605. It significantly increases total number of Concurrent Client Connections per CPU core.

  • 1 virtual appliance
  • 1 CPU core
  • 2 GB RAM
  • 50 GB HDD
  • RedHat, CentOS, Ubuntu

This configuration should not be used for production.

With an estimated load up to ~7.000 Concurrent Client Connections.

  • 2 virtual appliance
  • 2 CPU cores each
  • 4 GB RAM each
  • 50 GB HDD each
  • RedHat, CentOS, Ubuntu

This configuration should not be used for mission critical Applications because of limited high availability functions.

With around 50.000+ Concurrent Client Connections.

  • 4 physical appliances
  • 32 CPU cores
  • 64 GB RAM
  • 500 GB HDD
  • RedHat, CentOS, Ubuntu

We recommend using dedicated hardware appliances for loads higher than 7000 Concurrent Client Connections.

More than 300 000 Concurrent Client Connections.

  • 1x Cisco UCS B200 M4 Blade Server with 44 cores and 128GB RAM (front plane) per every 100 000 Concurrent Client Connections
  • At least 3 Blades for the front plane to ensure full high availability
  • 3x Cisco UCS B200 M4 Blade Server with 4 cores and 16GB RAM (back plane)
  • 100 GB SDD
  • RedHat, CentOS, Ubuntu

Software requirements

SeaCat Gateway is compatible with the following operating systems:

  • Ubuntu Linux 12+ LTS releases
  • CentOS Linux 6+
  • Red Hat Linux 5+
  • Debian Linux 7+
  • Slackware Linux 14+
  • Fedora Linux 22+
  • OpenSuse Linux 13+
  • SUSE Linux Enterprise Server 12+
  • Oracle Enterprise Linux 6.4+
  • Gentoo Linux
  • Apple Mac OS X

SeaCat Gateway may be built for any properly-designed Linux distribution, POSIX-compatible UNIX, and UNIX-based operating systems. Please contact TeskaLabs support for more information.

Network requirements


SeaCat Gateway is suited to operate at network perimeter in front of Application Backend inside Demilitarized Zone (DMZ). At least two network interfaces are needed, one for Public Network connection and another for Private Network connection. Network firewalls have to be configured accordingly. Interfaces speed reflects expected maximum Client Connection traffic bandwidth.

Public Network Interface

Public Network interface is used for communication over unsecured Public Networks such as the Internet or Internet service providers’ networks. One open TCP port is required per SeaCat Gateway. This port accepts connections from Clients to SeaCat Gateway. Strong encryption is assured by secure Client Connection via TLS. The Client Connections are inbound, opened by SeaCat SDK. It is recommended to use TCP/443 for maximizing network accessibility. The data traffic is not HTTPS, but it is compatible with SSL layer. If you want to prepend Load Balancing appliance in front of SeaCat Gateway, SSL passthrough functionality has to be enabled.

Private Network Interface

Private Network interface is used for communication between SeaCat Gateway and Application backends. SeaCat Gateway configuration allows more than one Application Backend. Protection of the communication depends on Private Network policies and Host ability. Host Connections are outbound, opened by SeaCat Gateway. Protocols such as HTTP, HTTPS, MQTT, CAN bus or other protocols commonly used by Application Backend are implemented.

Client Requirements

Application has to integrate SeaCat SDK to be able to communicate with SeaCat Gateway. The size of SeaCat SDK is approximately 700kB per CPU architecture. SeaCat SDK supports these platforms:

  • Android 2.3+
  • iOS 4.2+
  • Windows Mobile
  • Linux
  • Apple Mac OS X
  • Windows 7+