Spider Gadget
HomeCatalogueSpiderIQHardware Requirements
Infrastructure Guide

Hardware & System
Requirements

Minimum and recommended specifications for deploying SpiderIQ on-premise, in a private cloud, or on a managed VPS โ€” across all three plan tiers.

Min CPU

4 vCPUs

Starter tier

Min RAM

8 GB

DDR4 required

Min Storage

50 GB SSD

NVMe recommended

Min Network

100 Mbps

Outbound unrestricted

By Deployment Tier

Hardware Specifications

Minimum specs allow the platform to run; recommended specs ensure optimal scan throughput and report generation speed.

Starter

Up to 5 scan targets

ComponentMinimumRecommended
CPU
4 vCPUs / 2.4 GHz8 vCPUs / 3.0 GHz
RAM
8 GB DDR416 GB DDR4
Storage
50 GB SSD100 GB NVMe SSD
Network
100 Mbps1 Gbps
OS
Ubuntu 22.04 LTSUbuntu 22.04 / RHEL 9

Professional

Most Popular

Up to 25 scan targets

ComponentMinimumRecommended
CPU
8 vCPUs / 3.0 GHz16 vCPUs / 3.5 GHz
RAM
16 GB DDR432 GB DDR4 ECC
Storage
200 GB NVMe SSD500 GB NVMe SSD (RAID-1)
Network
1 Gbps10 Gbps
OS
Ubuntu 22.04 LTSUbuntu 22.04 / RHEL 9

Enterprise

High Availability

Unlimited targets

ComponentMinimumRecommended
CPU
16 vCPUs / 3.5 GHz32+ vCPUs / 4.0 GHz
RAM
32 GB DDR4 ECC64โ€“128 GB DDR5 ECC
Storage
1 TB NVMe (RAID-1)2 TB NVMe (RAID-10)
Network
10 Gbps25 Gbps redundant
OS
Ubuntu 22.04 / RHEL 9RHEL 9 / Rocky Linux 9
Cloud Deployments

Recommended Cloud Instances

Tested and validated instance types across the three major cloud providers.

ProviderStarterProfessionalEnterprise
AWSt3.xlarge (4 vCPU / 16 GB)m6i.2xlarge (8 vCPU / 32 GB)m6i.4xlarge (16 vCPU / 64 GB)
AzureStandard_D4s_v5 (4 vCPU / 16 GB)Standard_D8s_v5 (8 vCPU / 32 GB)Standard_D16s_v5 (16 vCPU / 64 GB)
GCPn2-standard-4 (4 vCPU / 16 GB)n2-standard-8 (8 vCPU / 32 GB)n2-standard-16 (16 vCPU / 64 GB)
Firewall & Connectivity

Network Requirements

Outbound HTTPS (443)required

Required for NVD CVE feeds, OSINT sources (crt.sh, c99.nl), and threat intelligence APIs

Outbound DNS (53 UDP/TCP)required

Subdomain brute-force and DNS resolution across all scan modules

Outbound HTTP (80)required

HTTP probe module and redirect chain analysis

Inbound HTTPS (443)required

Web dashboard access and REST API endpoint

Outbound SMTP (587)required

Email notification delivery via TLS

Outbound TCP (1โ€“65535)recommended

Full port scan coverage for IP Analysis module

Inbound SSH (22)optional

Administrative access โ€” restrict to management IPs only

Outbound NTP (123 UDP)recommended

Time synchronisation for accurate scan timestamps

Dependencies

Software Requirements

Runtime

  • Node.js 20 LTS (minimum 18 LTS)
  • npm 10+
  • Python 3.11+ (optional, for extended OSINT modules)

Database

  • PostgreSQL 15+ (production)
  • SQLite 3.40+ (development / Starter)
  • Redis 7+ (session store & job queue)

Web Server

  • Nginx 1.24+ (reverse proxy / TLS termination)
  • Certbot / Let's Encrypt (TLS certificates)
  • PM2 or systemd (process management)

Security

  • OpenSSL 3.0+
  • fail2ban (brute-force protection)
  • UFW or iptables (host firewall)

Containerised (optional)

  • Docker 24+
  • Docker Compose 2.20+
  • Kubernetes 1.28+ (Enterprise HA deployments)

Important Notes

All specifications assume dedicated resources. Shared hosting or burstable instances (e.g. AWS t3 burst credits) may cause scan timeouts under sustained load.

Subdomain discovery and full port scans generate significant outbound traffic. Ensure your hosting provider permits security scanning from your IP range, or whitelist your scanner IP with target organisations.

For on-premise Enterprise deployments, SpiderIQ supports air-gapped environments with offline CVE database sync. Contact info@spidergadget.io for the offline deployment guide.

SSD storage is mandatory. Spinning-disk HDDs will cause severe performance degradation in the scan result database and report generation pipeline.

Need a Custom Deployment?

Our team can help size your infrastructure, design an HA architecture, or provide an air-gapped deployment package for classified environments.