Inc - Globalscape

| Year | Milestone | |------|-----------| | | Founded as GlobalScape by former IBM engineers John R. McGowan and Robert W. Kessler in San Diego, California. The original focus was on network file‑sharing utilities for UNIX and early Windows environments. | | 1995 | Launch of File Transfer Protocol (FTP) Server for Windows NT—one of the first commercial FTP servers with GUI management. | | 1999 | Introduction of Globalscape Secure FTP (SFTP) , adding SSH‑based encryption to its product line. | | 2003 | Release of Globalscape Enterprise Server (GES) , a bundled solution that combined FTP, SFTP, and WebDAV with user management and logging capabilities. | | 2008 | Rebranding of Enterprise Server to Globalscape EFT , reflecting a shift toward Managed File Transfer (MFT) rather than simple protocol support. | | 2013 | Acquisition of Avaza (a workflow‑automation startup) – integration of process‑automation features into EFT. | | 2015 | Launch of EFT Cloud , marking the company’s first fully hosted, multi‑tenant SaaS offering. | | 2018 | EFT Edge introduced—lightweight, on‑premises agents designed for IoT and edge‑computing use cases. | | 2020 | EFT API released, enabling developers to embed secure file‑transfer capabilities directly into custom applications and CI/CD pipelines. | | 2022 | Global expansion: new data‑center regions in Frankfurt, Singapore, and São Paulo to support low‑latency compliance for GDPR, LGPD, and other regulations. | | 2024 | EFT Quantum‑Ready , a prototype architecture that leverages post‑quantum cryptography (PQC) algorithms for future‑proof encryption. | | 2025 | Strategic partnership with Microsoft Azure and Amazon Web Services (AWS) to provide native integration with Azure Blob Storage, S3, and Azure AD/Okta identity services. |

Globalscape plans to evolve EFT from a solution into a full‑stack data‑exchange platform that includes: globalscape inc

A collaboration with in 2025 produced EFT Sentinel , an AI module that monitors transfer patterns, flags anomalous volume spikes, and suggests remedial actions. Early results show a 42 % reduction in false‑positive security alerts compared with rule‑based detection alone. | Year | Milestone | |------|-----------| | |