Box holds your files well. It just can't let a partner log in over SFTP, take in files from an outsider, or show you who did what. Files.com adds all of that on top of any Box account, whether it's your own or a partner's, bank's, or investor's. People can send, receive, and share the files in it, and you get a full record of every action. You don't have to use Box yourself to trade files with someone who does.
Box is built for people working with documents inside one company. It was never built for partner logins over SFTP, automated file routing, or sending files out with a full record of who got what. Files.com mounts or syncs against any Box you can reach and adds that layer on top. It’s all controlled and logged from your side, without changing how anyone uses Box.
The Box account can be your own, or it can belong to a client, a bank, an investor, or a partner who runs on Box and expects you to deliver through it. Pull files out of a Box someone else owns, drop files into theirs, or do both at once. It’s all controlled and logged on your side, so you keep a record of every file you trade even when the Box isn’t yours. You don’t have to use Box yourself to trade files with someone who does.
Box can’t let a partner log in over SFTP. Files.com mounts a Box folder and adds SFTP, FTPS, FTP, and WebDAV on top of it from one place. Those are the ways partners and apps actually connect, so you stop turning down a partner who only speaks SFTP. They reach the files in Box without ever touching Box itself.
Box’s API names every file by a long ID code instead of by its path, so even grabbing /Clients/Acme/invoice.pdf turns into a chain of lookups. Files.com puts a normal path-based API, SDKs, and CLI in front of Box and does that translation for you, so your code just asks for files by their folder and name.
Mount the folder and Files.com passes every action through to Box in real time. There is no second copy and no migration, so the team that lives in Box keeps working exactly as before. When the Box belongs to someone else, a sync moves only the files the job needs, in the direction you pick.
Files.com shows Box right next to SharePoint, OneDrive, Google Drive, S3, Azure Blob, and your own servers in one place, so a single job can read from Box and write to a partner’s SFTP server without leaving Files.com.
When a file lands in the mounted Box folder, Files.com can email the right people, post to Slack or Teams, fire a webhook, or run a rule that moves, encrypts, or routes it. You get the alerts and routing Box leaves out, and there is no custom Box app to build.
Files.com adds a layer of control over Box content without touching Box’s own settings: who can see what, a record of everything that happens, and the same company logins your team already uses.
Hand each person, partner, or app the exact folders they need and nothing else, with nine levels of permission per user or group.
Every login, upload, download, and permission change against the Box content is logged in one place and can be exported to your security tools. Box’s own logging was never built to produce that record, so when the auditor asks who touched a file, you have the answer.
People sign in with your company login: Okta, Entra ID, Active Directory, Google, JumpCloud, OneLogin, Auth0, Duo, or any SAML provider. Two-factor is enforced right down to the SFTP, FTPS, and WebDAV connections. When someone leaves, you cut their Box access in one place, so a former employee can’t keep reaching files you forgot to lock down.
Files.com can apply GPG encryption and decryption automatically as files move, so sensitive data is protected before it lands. There is no manual step, no separate tool, and nobody has to remember to do it.
Mount a Box folder as a Files.com folder. Every action passes straight through to Box in real time, with no copy and no delay. Best when Files.com is the live way people and apps reach Box content.
Copy files on a schedule between Files.com and Box, in either direction, so the files end up in both places. Best for backups, archives, staged ingest, and the case where you only need to move part of someone else’s Box.
Run a rule when a file arrives, on a schedule, or when a condition is met, with the Box mount as the source, the destination, or both. Files.com treats a mounted Box folder exactly like its own storage.
Separately, you can let people sign in to Files.com with their Box login. This is its own setting, independent of the file connection above.
A partner uploads to your Files.com site over SFTP. The file lands in the mounted Box folder, Files.com sends an alert, and a rule routes it where it needs to go. The partner never gets a Box account.
An internal app reads and writes Box content through the Files.com API, CLI, FTP, or SFTP, addressing files by normal folder and name. You skip writing a direct Box integration, so the work that was a multi-week project ships in an afternoon.
Make a share link to a folder in Box, branded with your own domain. Recipients preview or download, every access is logged, and the files never leave Box.
Your team runs on SharePoint, Google Drive, S3, or your own servers, but a client, bank, or investor sends documents through their Box. Files.com syncs against that Box on a schedule to pull their files in or push yours out. It’s controlled and logged on your side, with no Box account for anyone on your team.
Take in files from outside people straight into a Box folder, with no Box account needed on their end, and every upload is logged.
Learn MoreSend Box files out with branded, tracked share links under your own domain, with expiration dates, watermarks, and recipient controls.
Learn MoreRoute files on the Box mount by event or schedule: move, encrypt, convert, and hand off, with no custom Box app to build.
Learn MoreEvery access, download, and permission change against the Box mount kept in a tamper-proof, exportable record. Box’s own logging does not provide it.
Learn MoreServe the Box folder over SFTP, FTPS, FTP, and WebDAV from one place. These are the connection methods partners and apps use that Box doesn’t offer.
Learn MoreMove and mirror files between Box and other servers or clouds on a schedule, for archives, staged ingest, and pipelines that span systems.
Learn MoreWhat buyers ask about how Files.com connects to Box, what it costs, and what the integration actually does.
Start a free 7-day trial. Connect a Box account, run a test transfer, and prove the integration works on your workflow. No credit card required.
No credit card required • 7-day free trial • Setup in minutes