Skip to content

System Requirements

This page outlines the hardware and network requirements for deploying ApiFort.

Hardware Requirements

Resource Allocation Requirements

ApiFort requires dedicated, non-overcommitted resources to function properly. Virtual environments must provide guaranteed resources that match the specifications below. Overcommitted or shared resources will result in performance degradation and potential system instability.

Select a configuration to view details

  • CPUs: 16
  • Memory: 48 GiB
  • Disk: 200 GiB (SSD storage recommended)
  • Traffic Capacity: Suitable for approximately 10 million requests per day
  • CPUs: 32 (dedicated cores, not shared/overcommitted)
  • Memory: 64 GiB (dedicated RAM, not shared/overcommitted)
  • Disk: 500 GiB (SSD storage required)
  • Traffic Capacity: Suitable for higher traffic volumes exceeding 30 million requests per day
  • The recommended configuration ensures optimal performance and scalability for your applications.

Node1: Apifort Core

  • CPUs: 24 (dedicated cores, not shared/overcommitted)
  • Memory: 48 GiB (dedicated RAM, not shared/overcommitted)
  • Disk: 500 GiB (SSD storage required)

Node2: Apifort Data

  • CPUs: 16 (dedicated cores, not shared/overcommitted)
  • Memory: 48 GiB (dedicated RAM, not shared/overcommitted)
  • Disk: 500 GiB (SSD storage required)

Node3: Apifort Processor

  • CPUs: 48 (dedicated cores, not shared/overcommitted)
  • Memory: 64 GiB (dedicated RAM, not shared/overcommitted)

  • Disk: 200 GiB (SSD storage required)

  • Traffic Capacity: Suitable for 50+ million requests per day

  • The high-capacity configuration ensures optimal performance and scalability for enterprise-level traffic volumes.

Traffic-Based Sizing Note

The hardware requirements may vary based on:

  • Request/response body and header sizes
  • Number of attack detection events
  • API traffic patterns
  • Data Storage Time

Network & Infrastructure Requirements

  • All 3 servers must be deployed on the same VLAN (Subnet)
  • Enterprise-grade network and disk performance required due to high I/O operations between servers
  • Additional network interface required for Processor node to handle mirrored traffic
  • Servers must be scalable if deployed in virtual environments

Network Requirements

Network Connectivity Requirements

Required Endpoint Access:

  • URL: https://kafeinproduct.blob.core.windows.net
  • Access Type: Persistent
  • Authentication: No special authentication required

This endpoint provides:

  • Docker installation packages
  • ApiFort application packages
  • System updates and patches

Network Configuration Notes:

  • Firewall rules should allow outbound traffic to this endpoint
  • No general internet access is required beyond this specific endpoint

Additional Network Considerations

Firewall Port Requirements:

Port Protocol Service Direction Description
80 TCP HTTP Inbound Web interface (redirects to HTTPS)
443 TCP HTTPS Inbound Secure web interface
9050 TCP HTTP Inbound Backend API
9094 TCP Kafka Inbound External Kafka listener
9095 TCP Kafka Inbound Kafka SSL listener

Internal Container Communication:

All containers communicate on the Docker internal network. No additional firewall rules are needed for internal container-to-container communication.