Hardware & Marketplace Requirements

This page contains the hardware requirements, CDN marketplace requirements and the recommended network configuration for OnApp CDN.

Hardware Requirements

These are the minimum recommended specs for OnApp CDN controller, edge and storage servers:

OnApp Controller ServerCompute Resource Servers

Backup Server

  • Dual or Quad Core 2Ghz+ CPU
  • 8GB+ RAM
  • 100GB RAID 1
  • 2x Gig network interface cards
  • CentOS 7 (x64)
  • 8GB RAM
  • Quad Core 2Ghz+
  • 200GB HD (SSD recommended)
    and no-raid setup
  • 3x Gig NIC (4 recommended)
  • CentOS 7 (x64)
  • 4GB RAM (8GB+ recommended)
  • Dual or Quad Core 2Ghz+
  • 2TB Storage mounted locally
  • 2x Gig NIC
  • CentOS 7 (x64)

Also below you can find hardware requirements for:

AcceleratorEdge and Storage Servers
  • Minimum requirements: 4 cores, 4GB of RAM and 100GB of storage
  • Recommended parameters: 8 cores, 16 GB of RAM and 1TB of storage
  • SSD is recommended to avoid slowing down access
  • Minimum requirements: 4 cores, 4GB RAM and 100GB of disk space (SSD recommended)
  • Recommended parameters: 8 cores, 16GB RAM and 1TB of disk space (SSD recommended)

CDN Marketplace Requirements

Edge servers submitted to the marketplace are assessed on a case-by-case basis before they are accepted. This helps us to ensure effective CDN performance for hosting providers and end users.

CDN storage server is not available in the marketplace (only HTTP and streaming edge servers are allowed).

The assessment process includes:


We benchmark your PoP via SSH. It must meet these minimum requirements:

  • Max marketplace price of $0.05/GB (EU/US) or $0.20/GB (rest of world)
  • Two or more dedicated edge servers on different compute resources (for redundancy)

Minimum edge server hardware/network/storage specs:

CPUQuad CoreQuad Core
Sequential Read45MB/s45MB/s
Port SpeedN.America/EUOtherN.America/EUOther

RAIDNone / RAID-0None / RAID-0
IPs3 Public IPs1 Public IP
Disk Space400 GB*1TB**1TB

* this configuration provides you with a small disk and good IOPS performance

** this configuration provides you with a large disk and lower IOPS performance

Location/Existing Coverage Assessment

Next, we consider your PoP's physical location. Our aim is to ensure broad CDN coverage while preventing saturation of edge servers in a given location.

  • A PoP in a new location is likely to be accepted as long as it passes the benchmark process.
  • In a location with many existing PoPs, your server may not be accepted unless it has unusually good performance characteristics.

Benchmark + Location = Decision!

If your PoP is accepted, it is available immediately on the marketplace.

  • If your PoP is not accepted for performance reasons, we'll raise a ticket for resolution with you, and keep it in view for reassessment in the future.
  • If location issues prevented your PoP being accepted, we'll keep in view for reassessment in the future.

Recommended Network Configuration