SnapLogic pipelines move files through File Snaps over SFTP and through S3 Snaps. Point both at Files.com and they land on one managed layer: partner intake, PGP, transformation, and monitoring built in, with pipelines kept for the data work they’re good at.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
SnapLogic’s binary Snaps are honest about what they are: readers and writers. File Reader, File Writer, and the recursive Multi File Reader move binary streams to and from SFTP, FTPS, and S3 endpoints. Everything about those endpoints is somebody else’s job: the server, the partner credentials, the keys, the monitoring, the archive.
Files.com is that somebody else. Pipelines read and write one managed layer over SFTP or the S3-compatible API. Partner onboarding, PGP, transformation, and monitoring run underneath as configuration, and the file-only pipelines retire into Automations.
File Snaps and S3 Snaps on one endpoint, intake before the sweep, and monitoring on every feed.
SnapLogic’s File Reader and File Writer Snaps move binary streams over SFTP and FTPS, and the Multi File Reader walks a directory tree recursively with wildcards. Point them at Files.com and every pipeline gets a managed endpoint with scoped credentials.
Pipelines that prefer buckets to folders can use SnapLogic’s S3 Snaps against the Files.com S3-compatible endpoint: same files, same permissions, whichever Snap fits the pipeline.
The files a pipeline processes start at counterparties. Each delivers into its own scoped folder over SFTP, FTPS, AS2, or a browser, so the Multi File Reader’s wildcard sweeps one clean tree instead of a shared dumping ground.
Run everything through SnapLogic and the connections keep coming: vendors, ERP feeds, HR systems. Each new flow is a folder and a credential on the same hub, not another server or another hand-built exchange.
Format conversion, splitting, renaming, and per-recipient encryption run as Automations and TransformScript on the platform, so pipelines keep their Snaps for the data work, not the file busywork.
A pipeline sweeping an empty folder succeeds at reading nothing. Delivery monitoring knows the window each upstream feed is due in and alerts when that window closes without files.
Everything the Snaps need on the endpoint side is configuration, not another server to run.
File Snaps authenticate with Basic or SSH Auth accounts from SnapLogic Manager. Files.com issues a scoped service user per pipeline family, with a permanent hostname and host key that never rotate out from under an account.
Snaplexes run pipelines in parallel, and Files.com allows 50 concurrent sessions per user. Parallel executions on one service account never queue behind each other.
S3 keys are issued per user and inherit that user’s folder permissions, so a pipeline connecting over the S3-compatible API sees exactly what its service account allows. Reads and writes land in the same audit log either way.
Counterparty encryption runs as folder settings, with every key in the platform’s key manager. Files decrypt before a pipeline reads them and encrypt after it writes, with no key handling in the pipeline.
Vendor-owned FTP servers and the manufacturer’s in-house ERP could keep working as they always had while Files.com reconciled the exchange between them.
Read The Story
Files.com gives automated partners and browser-only vendors the same branded exchange point within an integration estate of thousands of interfaces.
Read The Story
“Files.com's strengths are simplicity, ease of use, and the cloud connectors. We don't have to invent custom infrastructure for every partner.”
“Files.com is versatile — it can manage many different situations from a single platform. We've consolidated multiple tools onto it.”
“Files.com is robust and scales to a large enterprise. We get multiple files per minute, per second — and we're a 24/7 organization, so everything has to always be up.”
What integration teams ask most when wiring file work into SnapLogic pipelines.
SnapLogic connects to Files.com through the binary Snaps (File Reader, File Writer, and Multi File Reader) over SFTP or FTPS with a Basic or SSH Auth account, or through the S3 Snaps against the S3-compatible endpoint. Files.com’s hostname and host key are permanent, so accounts configured once keep working.
Yes. SnapLogic’s Multi File Reader reads directories recursively with wildcard patterns. Organize the Files.com tree per counterparty and the pipeline sweeps everything that arrived, while each sender stays scoped to its own folder.
File-shaped transformation runs on Files.com, as configuration. Format conversion, splitting, renaming, and per-recipient encryption run as TransformScript and Automations, not as pipeline steps. Pipelines keep the data work Snaps are built for.
Files.com handles PGP. Encryption and decryption run as folder settings with every key in the Files.com key manager. Pipelines read and write plain files, and no private key lives in a Snap configuration.
However they can: Files.com accepts SFTP, FTPS, FTP, AS2, the S3-compatible API, a browser upload, or an email inbox that turns attachments into files. Each sender gets its own scoped credential and folder.
Yes. When a pipeline is really file movement with transformation (read, convert, rename, deliver), a Files.com Automation covers it with one less pipeline to maintain. SnapLogic keeps the work that touches APIs and data records.
Yes. Files.com webhooks fire on upload events, so a triggered task can start the moment a counterparty’s file lands instead of on the next scheduled sweep.
Files.com delivery monitoring defines the window each feed is due in and alerts when a window closes without files, so a pipeline that swept nothing gets noticed the same hour.
Yes. Files.com holds SOC 2 Type II, offers a pre-approved HIPAA business associate agreement with Files.com Enterprise, encrypts in transit and at rest, enforces least-privilege folders, and keeps a complete audit log of every file a pipeline read or wrote.
Files.com replaces the SFTP server somebody ran for the pipelines to sweep, plus the onboarding, key handling, transformation, monitoring, and archive nobody built around it. The pipelines keep their Snaps. The layer under them becomes a service Files.com runs.
Partner intake, every protocol, PGP, and transformation: the File Orchestration Platform underneath SnapLogic, so pipelines do only the data work.
No credit card required • Free for 7 days • Live in minutes