This article outlines the key architectural and hosting elements of the Files.com platform, including our use of AWS, deployment model, data center safeguards, and more. These practices are reviewed annually as part of our SOC 2 Type II audit.

Technology Stack & Architecture

Files.com operates a sophisticated cloud environment hosted on Amazon Web Services (AWS). We run hundreds of virtual machines across multiple AWS regions and use industry-standard tools and systems. All infrastructure is time-synchronized using Network Time Protocol (NTP).

Our platform is composed of modular components built in Java, Ruby, Go, JavaScript, Python, and other languages. These services are deployed across virtual machines.

Containers are used selectively to isolate high-risk processes such as document previews, scanning for malware (note: this feature is not generally available), file conversions, and compression or extraction workflows.

Network Diagram & Data Flow Diagrams

Files.com maintains detailed network and data flow diagrams that describe our technical architecture. While these materials are proprietary and not shared externally, they reflect the full system lifecycle from development through production. These artifacts are reviewed as part of our SOC 2 audit process.

On-Premise, Hybrid, & Cloud Deployment Models

Files.com is a fully cloud-hosted SaaS platform. It cannot be run as an on-premise or self-hosted application. The platform is accessed over the public internet and does not require a VPN or private network connection.

To support hybrid cloud use cases, Files.com offers an optional agent and SDKs that can be deployed inside a customer’s private environment. These tools allow customers to bridge on-premise storage and internal systems to Files.com.

Software Applications

Files.com includes a wide range of supported applications and tools, all covered under our Software Development Life Cycle (SDLC). These include:

• Web application
• Desktop apps for Windows and Mac
• Mobile apps for iOS and Android
• Cross-platform Command Line Interface (CLI)
• Open source SDKs in multiple languages

Cloud Infrastructure, Data Centers, & Hardware Hosting

Files.com does not own or operate its own data centers. All infrastructure is hosted on Amazon Web Services (AWS), which manages all hardware, system maintenance, and physical access. AWS holds ISO 27001 certification and completes regular SOC 2 Type II audits, which Files.com reviews annually as part of our vendor risk management program.

Hardware specifications are not disclosed by AWS. Files.com relies on AWS to ensure redundancy, perform maintenance, and manage the infrastructure lifecycle.

Physical Security & Environmental Controls at AWS

AWS data centers implement rigorous physical and environmental safeguards. Facilities are nondescript and tightly controlled, with 24/7 professional security staff, biometric authentication, surveillance, and intrusion detection systems. Access to data center floors requires multi-factor authentication and is limited to individuals with a valid business need. All access is logged and audited.

Environmental protections include smoke detection, fire suppression systems, climate control to regulate temperature and humidity, and fully redundant power systems with uninterruptible power supplies (UPS) and backup generators.

Files.com Office Security

Files.com maintains two physical office locations. These sites do not house production infrastructure or privileged customer data.

Office computers function as remote workstations and connect to internal systems via secure, on-device VPN. Physical entry to offices is controlled via badge systems. Non-employees must be escorted at all times. Offices are protected by monitored alarm systems, and all physical access is logged and audited.

Time Synchronization

All Files.com systems are synchronized using industry-standard NTP sources to ensure accurate timestamps across infrastructure.

Code Escrow

Files.com does not use third-party code escrow services.

Log4j Vulnerability

Files.com responded promptly and transparently to the 2021 Log4j vulnerability. Read our full response.