· 1:28 Central Documentation - FileCatalyst Downloads Web browsers allow the administrator to view and administer the system. There is typically no need on the administrator's end to c... FileCatalyst Downloads FileCatalyst Service for Accelerated File Transfer - GoAnywhere FileCatalyst Service in GoAnywhere MFT. ... The FileCatalyst Service is a file transfer acceleration protocol in GoAnywhere that c... GoAnywhere MFT Introducing TransferAgent in FileCatalyst Workflow - GoAnywhere What & How. FileCatalyst Workflow acts as a web-based portal for any file transfer needs, as John calls it, “the Swiss Army knife ... GoAnywhere MFT FileCatalyst Reverse Proxy Getting Started Guide FileCatalyst Reverse Proxy allows a FileCatalyst Server to be completely isolated behind a firewall, with no incoming ports open a... FileCatalyst Downloads Getting Started with FileCatalyst’s Accelerated File Transfer Solution FileCatalyst's Acceleration Technology: How it Works ... FileCatalyst's core transport technology is based on the UDP protocol, wh... GoAnywhere MFT FileCatalyst Server and Client Port Configuration and ... Port 990 for TCP. This Port is secured over SSL and is also used as the communication channel. The default value of 990 can also b... Fortra Support Portal FileCatalyst Service in GoAnywhere MFT FAQs. What is FileCatalyst Acceleration? FileCatalyst solutions use multiple acceleration techniques to deliver speedy file transf... GoAnywhere MFT FileCatalyst Server Documentation Using FileCatalyst Server Admin. Connections. Administration Filters. HTTP Settings. HTTP Access. Enabling AJP Connector. HTTP Upl... FileCatalyst Downloads Fortra's FileCatalyst - Accelerated File Transfer Solution for ... Fortra's FileCatalyst - Accelerated File Transfer Solution for Large Files. ... FileCatalyst is a UDP-based protocol, which makes ... Bulwark Technologies FileCatalyst Central - connect distribution Each FileCatalyst product serves a unique set of organizational file transfer needs and works across a variety of industries. On i... connectdistribution.pl Server Documentation - FileCatalyst Downloads 2. n Authentication Services (LDAP, RDBMS, PAM) In addition to the internal user definitions, FileCatalyst Server allows the integ... FileCatalyst Downloads
FileCatalyst Internal refers to the core architecture, proprietary protocols, and internal system components that enable high-speed, accelerated file transfers. Developed by Fortra, FileCatalyst is designed to overcome the inherent limitations of traditional TCP-based protocols like FTP, especially over networks with high latency or packet loss. The Core Architecture The FileCatalyst ecosystem operates on a client-server architecture . For the system to work internally, the software must be installed on both ends of the network: FileCatalyst Server: The central engine that manages users, security, and storage. It serves as the endpoint for all transfers and can connect to on-premise storage or cloud-based object stores like Amazon S3 and Microsoft Azure Blob. Client Applications: Various "internal" client tools interact with the server depending on the use case: HotFolder: For automated, scheduled transfers and folder replication. TransferAgent: A lightweight web plugin that allows browser-based acceleration. Mobile App: For uploads and downloads from iOS or Android devices. SDK/APIs: For developers to integrate acceleration directly into third-party apps. Proprietary UDP Acceleration FileCatalyst | Fast File Transfer Solution - GoAnywhere
FileCatalyst Internal: Architecture, Protocol Mechanics, and Operational Advantages Abstract FileCatalyst is a proprietary high-speed file transfer solution designed to overcome the limitations of traditional TCP-based protocols (e.g., FTP, HTTP, SCP) over high-latency and high-packet-loss networks. This paper examines the internal architecture of FileCatalyst, focusing on its UDP-based file transfer protocol, congestion control algorithms, security model, and system components. Understanding these internals is critical for network engineers, system architects, and IT decision-makers deploying the solution in WAN, satellite, or mobile environments. 1. Introduction Standard TCP’s congestion avoidance (AIMD) significantly reduces throughput on long-fat networks (LFNs) or lossy links. FileCatalyst replaces the transport layer with a proprietary UDP-based protocol that decouples reliability from congestion control. Internally, the system is built for speed , resilience , and fine-grained control . 2. Internal Architecture Overview FileCatalyst follows a client-server model but can also operate in agent-based or peer-to-peer modes. The core internal components are: | Component | Function | |-----------|----------| | FileCatalyst Transfer Engine | Core protocol implementation; manages UDP sessions, retransmissions, and block-level logic. | | Central Server | Manages users, transfers, and licensing; maintains transfer history and logs. | | HotFolder | Watches directories for new files and automatically initiates transfers. | | WebApp / CLI | Administrative interfaces to control transfer parameters (bandwidth, encryption, parallelism). | | Agent | Lightweight service that enables delegated transfers between remote sites. | 3. The Internal Transfer Protocol FileCatalyst does not use standard TCP or UDP-based variants like UDT or QUIC. Its proprietary protocol is structured as follows: 3.1 Packet Structure (Simplified)
Header – Sequence number, transfer ID, flags (ACK, NACK, data, control). Payload – Encrypted file blocks (default block size ~128KB–1MB, configurable). Control messages – Rate update, heartbeat, termination, checksum. filecatalyst internal
3.2 Reliability Mechanism
Selective ACK (SACK) – The receiver periodically sends ACK maps indicating which blocks have arrived. Negative ACK (NACK) – Instead of waiting for timeouts, missing blocks are requested immediately. Forward Error Correction (FEC) – Optional internal redundancy (e.g., Reed-Solomon) to reconstruct lost packets without retransmission.
3.3 Congestion Control (Internal Algorithm) Unlike TCP’s loss = congestion, FileCatalyst’s internal controller distinguishes between: · 1:28 Central Documentation - FileCatalyst Downloads Web
Random packet loss (common on wireless/satellite) – does not throttle aggressively. Bufferbloat / congestion – detects rising one-way delay and reduces send rate.
The algorithm uses:
Delay-based probing – adjusts window based on observed RTT changes. Loss discrimination – moderate loss (up to 5-10%) triggers no backoff; high loss triggers rate halving. Bandwidth estimation – uses packet-pair or packet-train probing. FileCatalyst Workflow acts as a web-based portal for
This allows full utilization of a 100 Mbps link with 300 ms RTT and 2% loss, where TCP would drop to <5 Mbps. 4. Internal Security Model FileCatalyst secures data in transit without relying on TLS/TCP’s overhead:
Encryption – AES-256 in GCM mode (authenticated encryption) per packet. Key exchange – RSA-2048 or pre-shared keys (PSK) for control channel. Certificate-based authentication – mutual auth between client and server. Optional FIPS 140-2 mode – for government/defense deployments.