Files.com turns each custodian, broker and administrator connection into configuration: files are pulled from or pushed to the counterparty on its schedule under your own hostname, decrypted, renamed and routed in flight, and landed in storage you control. No counterparty changes how it delivers, and no application that reads the landing folders is rewritten.
Each counterparty dictates its own protocol, credentials, filenames, encryption and cutoff. Meeting all of them with a self-hosted SFTP server, rename scripts on a job scheduler and a person on a desktop client means every new counterparty is more code to write and watch, and a late file is a portfolio problem before anyone notices.
A custodian will not change its protocol for you. The prime broker will not rename its files. The administrator encrypts with its key and deletes after a week. Every one of those terms used to become a script somebody wrote and somebody else inherited, on a server IT would rather not run.
On Files.com each term is a setting on a connection: the schedule, the pattern, the key, the rename, the destination. The files land where the portfolio system already looks, the firm keeps its own copy, and the one that is late is an alert rather than a discovery at the open.
Real companies. Real file flows. Real results.
Positions and holdings in from every custodian, NAV and pricing from administrators and vendors, trade and position files out, and the compliance extracts around them.
Files.com pulls the overnight positions, holdings and cash files from each custodian’s and prime broker’s SFTP on its schedule, decrypts them, and lands them in the folder the portfolio system reads, before the trading day.
Fund administrator NAVs, pricing-service files and ratings arrive from each vendor’s endpoint under the firm’s own hostname and are renamed and routed in flight to the systems that consume them.
Daily holdings, trade and position files go to multiple custodians and banks over SFTP with the exact filename each requires, encrypted with its key, on its cutoff.
Compliance vendors, auditors and clients get their extracts from scoped folders on schedule, with every delivery recorded.
Configuration per counterparty, transformation in flight, an archive the firm owns, and an alert for the file that is late or short.
A custodian connection is a sync with the partner’s host key pinned, its credential held on the platform, a filename pattern, a schedule and a folder. The next counterparty is set up in an afternoon, with nothing for a developer to write or watch.
PGP decryption, renaming to the fixed names your batch jobs expect, and routing to S3, Azure or an on-premises landing folder through the Files.com Agent happen as the file arrives, so the applications that read the landing folders never change.
Files are archived to storage the firm controls with a retention rule, so the custodian’s seven-day window stops being the firm’s record.
Expectations know the positions file is due by six and must exceed a minimum size, and operations hears about a miss while there is time to call the custodian.
Files.com preserves the SMB paths behind Calamos’s batch estate, lets vendors cut over one at a time, and sends migrated analytics feeds to Azure without a second copy job.
Read The Story
Each new deal’s counterparty feed is now a matter of configuration rather than another engineering project.
Read The Story
One in-house-managed exchange now routes multiple terabytes of regulated data between counterparties’ existing transfer methods and the firm’s modern cloud systems.
Read The Story
Remote Server Mounts gave partners a managed, branded SFTP endpoint while routing investment files into storage accounts Fisher Funds controls.
Read The Story
“Simplicity, reliability, and speed of use. The uptime alone has been worth it — we've barely had a downtime issue.”
“The biggest challenge that Files.com helps us solve is keeping our file transfers secure. We rely most on the ability to keep our data encrypted while it’s stored at rest as well as in transmitting the data.”
The three ways custodian files move today, and where each one puts the risk.
IT patches and replicates the server, a job scheduler runs the rename and sync scripts, and every new counterparty is more code to write and watch.
Someone logs into each custodian portal each morning, pulls, renames and drops the files. A late file is a portfolio problem before anyone notices.
The custodian keeps files for a week and then deletes them. The firm’s own record is whatever someone happened to download.
What operations and IT teams at investment firms ask before moving counterparty exchange onto Files.com.
Set up each counterparty as a Files.com sync. Files.com connects to the custodian’s or administrator’s SFTP endpoint on the schedule you set, pulls the files that match a pattern and date, decrypts and renames them, and lands them in the folder your portfolio or accounting system reads. Outbound files go the same way in reverse, with the filename each counterparty requires, and every run is logged.
Keep the landing folders and filenames your batch jobs watch, on your own storage or an on-premises server the Files.com Agent writes to, and let Files.com deliver the same files there on the same schedule. Counterparties that push to you connect to your hostname on Files.com, with the hostname and host key preserved if you move the DNS, which is the SFTP server replacement playbook.
Yes. Attach the PGP key to the counterparty’s folder and mount your bucket as the destination through the Amazon S3 or Azure Blob integration. Files decrypt on arrival and are written into your storage as objects, so the analytics stack reads plaintext from your own bucket and no one runs a decryption step.
One automation per custodian renames the file the system wrote to the pattern that custodian mandates, encrypts it with that custodian’s key, and delivers it to its endpoint before its cutoff. Adding a custodian is another rule rather than another script.
Yes. A scheduled sync pulls every new file from the custodian’s directory into a Files.com archive folder on storage you control, and a retention rule keeps it for the period your record-keeping obligations require.
Yes. A sync or automation filters by filename pattern and modification date, so only the report types you use are pulled, and yesterday’s files are not pulled again.
Yes. Files.com pulls from the first counterparty and delivers to the second on arrival, renaming and encrypting in between as each requires, so an administrator’s file reaches a custodian, or a pricing file reaches an outsourced middle office, with no one in the loop.
A delivery expectation on each custodian’s folder knows the file’s window, its expected count and its minimum size, and alerts operations in email, Slack or Teams the moment a window closes short, with the record kept for the auditor.
Files.com provides SOC 2 Type II and PCI DSS attestations, dedicated IP addresses the counterparty can allowlist, PGP by folder rule and an immutable audit log, and has run as a managed service for 15+ years with zero breaches. The counterparty connects to a hostname on your domain and never sees a shared cloud range.
Each custodian, broker and administrator as a configured connection, files decrypted and renamed in flight, an archive the firm controls, and an alert before the trading day. Talk to us about the counterparties you exchange files with.
No pushy sales process
