When to Use the On-Premise Agent

The Files.com Agent connects internal file systems behind your firewall to the Files.com platform. It runs on a server inside your network and gives Files.com controlled access to local storage that would otherwise be unreachable from the cloud.

This guide covers when the Agent is the right fit, the workflows it supports, and the situations where it adds no value.

When to Use the Agent

Connecting to Internal Systems

Many organizations keep files on file servers, NAS (CIFS, SMB, NFS), or databases that sit behind a firewall and are not exposed to the public internet. The Agent connects from inside your network outward to Files.com, which lets Files.com reach those systems without changing how they are exposed.

Transferring Data Between Files.com and Local Infrastructure

When workflows move data regularly between Files.com and on-premise storage, the Agent handles the transfer. It works with Windows file shares, Linux servers, and dedicated backup storage. The direction is bidirectional: data can be pulled into Files.com or pushed back out to a local destination.

Automating Scheduled File Jobs

The Agent integrates with Files.com automations, so scheduled syncs and file jobs against on-premise storage run without additional middleware or scripting.

Connecting Without Reconfiguring Firewalls

The Agent connects to Files.com over an outbound connection. There is no need to open inbound ports, change firewall rules, or set up a VPN. That makes the security review shorter and keeps your network policy intact.

High-Performance Transfers

The Agent uses UDP-based transmission, which can move large files and large volumes of data faster than connections that rely on standard remote transfer protocols.

What the Agent Does

The Agent is installed on a local system or server inside your network. Once it is running, Files.com can interact with on-premise or network-attached storage as if those files and folders were part of the Files.com environment. Your local infrastructure becomes a source or destination for automations, workflows, integrations, and secure file sharing.

Data moves in both directions: pulled into Files.com from local systems, or pushed from Files.com to a local target. The same workflows can include third-party cloud storage, so cross-environment transfers do not require re-architecting your infrastructure.

The Agent is remote-controlled entirely from your Files.com site. This is the key difference from the Files.com Command Line Integration (CLI) app, Desktop App, and other clients: no operator is needed on the host system, so transfers run unattended.

Business Workflows and Use Cases

Many organizations keep on-premise systems in place for regulatory, operational, or performance reasons. The Agent connects those systems to the rest of the file-sharing ecosystem without forcing a migration, which fits well during a move to a hybrid environment.

A common pattern is an organization receiving data files on local systems from manufacturing devices or financial systems. With the Agent, those files sync to Files.com and become accessible to teams, partners, and automations. The reverse pattern also works: files placed in a Files.com folder get pushed automatically to a designated location on a local system.

The Agent is also useful when data must stay on a local network for compliance reasons but still needs to participate in broader processes like reporting or archival. The Agent acts as a conduit so cloud workflows can reach those files without exposing the underlying systems.

Paired with the Remote Server Mount feature, the Agent lets you reach on-premise locations through the Files.com web interface and mobile app, so remote users can interact with on-premise data from any device.

Problems the Agent Solves

The most common problem the Agent addresses is integrating legacy or isolated systems into modern file workflows. Without it, organizations fall back on manual processes, third-party file movers, or insecure workarounds to bridge on-premise systems and the cloud. Those approaches add operational complexity, security exposure, and compliance risk.

The Agent also addresses siloed data. A local storage folder becomes a connected node in your Files.com environment, and files move across departments, partners, and systems without duplication or manual handoff.

From an IT perspective, the Agent centralizes control over transfers, permissions, and logging. It removes the need to maintain standalone FTP servers or VPN setups for file movement.

When the Agent Is a Good Fit

The Agent fits businesses with critical file workflows tied to local storage that need to integrate with Files.com without reconfiguring infrastructure. It works well for organizations on a hybrid IT strategy, where cloud adoption is underway and local systems are still essential.

It also fits teams that collect files from users or partners into a local system and want the automation, auditing, and sharing features Files.com provides. When compliance requirements dictate local storage of sensitive data, the Agent gives you cloud workflows on top of that local storage without moving the data.

When the Agent Is Not Needed

If your business is fully cloud-based or your files already live in a cloud platform Files.com integrates with directly, the Agent is unnecessary. Files.com's direct integrations with Amazon S3, Azure, Dropbox, and others cover those workflows without local software.

The same applies if your organization has no on-premise systems in its file workflows, or if your workflows are limited to browser-based uploads and downloads. The Agent adds complexity without a corresponding benefit in those cases.