Operations — Filecatalyst

| Feature | FileCatalyst | FTP over TCP | Aspera (FASP) | Signiant (UDP) | |---------|--------------|--------------|----------------|----------------| | Protocol | Proprietary UDP | TCP | Proprietary UDP | Proprietary UDP | | Packet loss recovery | Selective retransmit | Retransmit all after loss | Selective + FEC | Selective | | Latency efficiency | Excellent | Poor | Excellent | Excellent | | Encryption | Built-in (TLS) | Optional (FTPS) | Built-in | Built-in | | Management console | Central | None | Console | Web-based |

Operational teams frequently encounter the following scenarios: filecatalyst operations

| Factor | Impact on FileCatalyst | |--------|------------------------| | | Linear scaling – can saturate 1 Gbps, 10 Gbps, or 100 Gbps links. | | Latency (RTT) | Minimal impact up to ~300 ms; still efficient at 600 ms (e.g., satellite). | | Packet loss | 1-5% loss: TCP may drop to <10 Mbps; FileCatalyst retains >90% of bandwidth. | | CPU resources | AES encryption + FEC adds load; modern multi-core systems handle 10 Gbps+. | | Disk I/O | Can become bottleneck – NVMe/SSD recommended for 10 Gbps+ transfers. | | Feature | FileCatalyst | FTP over TCP

FileCatalyst Central provides real-time operational visibility: | | CPU resources | AES encryption +

To maintain a healthy FileCatalyst environment, the following operational procedures are recommended:

: The central hub that manages users, security, and file systems. It typically runs as a 64-bit service on Windows or Linux.

While powerful, FileCatalyst is not a universal solution: