Client Apps vs. Server-Side Integration Tools

Files.com tools fall into two groups. Client-side tools are started by a person and run on a desktop, laptop, mobile device, or browser. Server-side tools run in the background, on servers or in cloud environments, without user involvement. This guide describes both groups and helps you pick the right one for a given workflow.

Client-Side vs. Server-Side

Client-side tools handle interactive tasks, one-time operations, and administrative actions — anything where a person needs to make a judgment or touch a file directly. Files.com client-side tools include the Web App, Desktop App, Mobile App, and Command Line Interface (CLI).

Server-side tools are built for scheduled jobs, unattended transfers, and large-scale integrations. They run for reliability and scale. Files.com server-side integration tools include Remote Servers, the Files.com Agent, and Automations.

Web App, Desktop App, and CLI

Client apps cover the human-driven tasks: uploading, downloading, deleting files, checking settings, configuring syncs and automations, managing users, and assigning folder permissions. They give users either a graphical interface or a command line for direct interaction with Files.com.

The Web App is used by both end users and Site Administrators. End users upload, download, rename, and organize files in the browser, and can edit and co-author through the Files.com editor. Site Administrators use the Web App to configure folder settings, manage user permissions, review logs, create automations, set up syncs, and handle other site-level administrative work.

The Desktop App gives users a mapped drive on their local machine. Files.com appears in the operating system's file explorer, and users open, save, and move files as if they were stored locally. A finance user can drag invoices into a department folder each week through Desktop App. A designer can open a media file from the mounted drive, edit it, and save it without an upload step.

The Mobile App provides access from smartphones and tablets. It supports basic file operations like viewing and downloading, which is useful for teams who need files while traveling or away from a desktop.

The CLI is a command-line utility for scripted or manual tasks. Developers and administrators use it for uploads, downloads, and folder management from a terminal. It also handles administrative configuration: onboarding users, retrieving reports, managing folder permissions, and automating recurring admin actions. The CLI fits well into development workflows and quick administrative tasks run directly from the terminal.

On-Premise Agent, Syncs, and Automations

The Files.com On-Premise Agent connects your Files.com site to internal systems such as file servers, network-attached storage (NAS), and other storage devices located in data centers or environments protected by firewalls. It runs as a background service on a server inside your infrastructure and establishes a secure outbound connection to Files.com, which gives access to systems that are not exposed to the public internet.

The Agent fits workflows that move data regularly between Files.com and your on-premise environment. It handles automated transfers from sources like Windows file shares, Linux servers, or internal backup storage, in either direction — uploading data to the cloud or pulling reports, logs, or media files back to local systems.

Syncs transfer files between Files.com and external storage systems automatically. The external side can be SFTP, SMB, S3-compatible storage, or other remote servers. Syncs run on a defined schedule and copy or mirror files in either direction.

Automations let you create rules that act on files when certain conditions are met. The rules can move, delete, or rename files based on file name patterns, file age, or upload location. Once configured, they run without intervention and enforce your business rules across folders and file types.

iPaaS and Infrastructure Tools

Files.com integrates with iPaaS platforms such as Zapier, Boomi, and MuleSoft for cross-application workflows. These platforms move data between Files.com and other tools like CRMs, ERPs, or data warehouses. A common pattern is pushing a signed contract from Files.com to a CRM when a new document is uploaded to a specific folder. These workflows are server-side because they run without user action.

Infrastructure automation tools follow the same distinction. The Files.com Terraform integration is typically used on the client side. DevOps engineers run it manually or through CI/CD to create or update Files.com configurations using infrastructure-as-code principles. That makes it a client-driven but scriptable integration.

The Files.com RClone integration is commonly used in server-side automation. It is installed on a server and run as part of a scheduled job or cron process to sync large volumes of files between Files.com and other cloud or on-premise storage systems. Because it runs in the background without user intervention, RClone fits the server-side automation model.

Choosing the Right Tool

Use client-side tools when human involvement is part of the workflow. The Web App, Desktop App, CLI, and Terraform fit tasks that require manual oversight, interactive file access, or administrative configuration.

Use server-side tools when workflows need to run in the background or at scale. The On-Premise Agent, Syncs, Automations, iPaaS integrations, and RClone fit unattended operations, system-to-system file transfers, and policy enforcement.