Filecatalyst Infastructure //free\\ Jun 2026

| Model | Use Case | Key Infrastructure | |-------|----------|---------------------| | | Small team, direct transfers | 1x Server + 1x Central | | DMZ + Internal | Secure enterprise (media, finance) | Gateway (DMZ) → Internal storage (behind firewall) | | Multi-site | Global file distribution | Multiple Gateways + Central hub | | Cloud Native | SaaS, burst transfers | Auto-scaling containers (K8s) + S3 backend | | Hybrid | On-prem + cloud archival | On-prem Server + cloud object storage plugin |

Unlike standard HTTP/FTP transfers, FileCatalyst relies on a proprietary UDP-based protocol and a unique architecture to achieve speeds up to 10 Gbps. Therefore, the infrastructure requirements differ significantly from standard web servers. filecatalyst infastructure

A unified web console that provides a "single pane of glass" view for monitoring the entire deployment. It allows administrators to remotely configure nodes, view real-time transfer histograms, and set alarms for system failures. Deployment Models | Model | Use Case | Key Infrastructure

FileCatalyst is a designed to overcome the limitations of TCP (latency, packet loss). Its infrastructure is built on three core pillars: It allows administrators to remotely configure nodes, view

Unlike traditional FTP or HTTP, FileCatalyst does not require proprietary hardware; it runs on standard Linux, Windows, or cloud instances.

Because this infrastructure often handles sensitive or proprietary data (like unreleased films or genomic sequences), security is baked into the foundation:

[Remote User] --UDP--> Internet --(Port 33000-33020)--> [Firewall] --> [DMZ Gateway] | v [Internal AD] <--LDAP--> [FileCatalyst Central] <--REST--> [Internal Storage (Isilon)] | v [On-prem Client] --UDP--> [FileCatalyst Server] <--Plugin--> [S3 Cloud Archive]