The Designs Stay On Your Own Share
The Files.com Agent fronts the on-premises design share where the drawings already live, over an outbound-only connection. Outsiders reach the project folder through Files.com; the DMZ FTP server is switched off.
Files.com gives every client, partner, and project its own scoped space that outsiders reach by browser, SFTP, or link, moves drawing sets and scan data at any size, and records who took what for as long as the job runs. Revisions, submittals, and field data come back through the same space.
Email bounces the plan set. The consumer tool caps out or gets blocked. Inviting every subcontractor into the collaboration suite widens your identity boundary, and the FTP server in the DMZ has standing logins nobody cleans up.
A drawing set runs to gigabytes. It goes to a client, a subcontractor, a bidder, and a consultant, none of whom work for you, and comes back revised. The exchange lasts as long as the project, and the record of who received which revision matters for years after.
Email, consumer tools, guest accounts, and the DMZ FTP server each fail one of those three tests, which is why most firms run all four at once. On Files.com every project is a scoped space, every outsider reaches it without joining your tenant, and the log answers who took what.
Real companies. Real file flows. Real results.






















A space per project, links for the outsider without an account, an intake for what comes back, and transfers that do not care how big the file is.
Each project gets its own folder tree on your branded site, with the client and its subcontractors as scoped users who see that project and nothing else. When the job closes, the accounts expire with it.
A share link under your domain hands a 10 GB drawing set to a consultant or bidder who will never be a user, with a password, an expiry, and a record of who downloaded it. Nothing to install on their side, and nothing left open on yours once the bid closes.
An Inbox on the project takes revisions, submittals, site photos, and scan data from outside firms through a browser, each submission private to its sender, with the project team notified on arrival.
Files up to 5 TB transfer in parallel chunks and resume after a dropped connection, in the browser, the desktop app, or over SFTP. A point-cloud dataset or a full plan set moves in one pass instead of being split, zipped, and re-sent.
The exchange sits in front of the storage you already run. Nothing has to move to be shared.
The Files.com Agent fronts the on-premises design share where the drawings already live, over an outbound-only connection. Outsiders reach the project folder through Files.com; the DMZ FTP server is switched off.
A Remote Server Mount puts the project exchange in front of the Azure Blob or Amazon S3 storage you already run. Nothing is migrated and nothing is stored twice.
Engineers and project managers sign in through single sign-on and are provisioned from the directory. Clients and subcontractors get scoped logins or links that expire, so the identity boundary of your collaboration suite never widens to include them.
Read-only accounts and always-on access logs kept garment plans on Jockey's sanctioned path and every download on the record.
Read The Story
Files.com gave hundreds of overseas vendors managed access to the existing design archive while preserving the workflows and logins they already knew.
Read The Story
The replacement had to preserve easy vendor access while bringing share-link restrictions, retention, and authentication under IT control.
Read The Story
Files.com preserved the factory’s existing SFTP workflow while giving Tellabs directory-driven access, directional permissions, and unified logging.
Read The Story
“We tested about five different cloud FTPs and Files.com had much faster download and upload speeds. Plus they have a great user interface with a lot of features.”

“As a large furniture manufacturer handling a high volume of high-resolution images, it makes everything effortless. The platform is secure, easy to use, and reliable — even when transferring large files.”

Every firm runs some mix of these today. Each one fails a different test.
Email bounces the plan set on size. The consumer tool caps out, gets blocked by the counterparty’s web filter, or puts the firm’s most external-facing work outside IT’s control. Either way someone splits the file and sends it three times.
Inviting every subcontractor and bidder into SharePoint or the company drive means every one of them is now an identity in your tenant, with access that outlives the project and permissions nobody reviews.
A standing per-vendor login on an internet-facing box, unpatched because the projects on it are live, with no record of who took what. It survives every audit until the one it fails.
What IT administrators and project teams ask before moving project-file exchange onto Files.com.
Put the set in the project folder on Files.com and send a share link under your own domain, with a password and an expiry if you want them. The recipient opens the link in a browser and downloads at full speed, with no account and nothing to install. Files up to 5 TB transfer in resumable chunks, and the audit log records who downloaded what.
Yes. Each project gets its own folder tree, and the client’s staff and subcontractors get logins scoped to that project alone. Nine permission levels decide who can upload revisions, who can only download, and who administers the folder, and the accounts can be set to expire when the project closes.
Attach a Files.com Inbox to the project: a branded upload page the outside firm opens in a browser. Submittals, site photos, and scan data land in the project’s intake folder, each submission private to its sender, and the project team is notified the moment a file arrives.
Yes. The Files.com Agent runs inside your network and fronts the design share over an outbound-only connection, so outsiders reach the project folders through Files.com while the files stay where they are. Retiring the server without partners changing anything is its own job, and this one runs on top of it.
From one stored copy, over SFTP or a share link. Files.com transfers single files up to 5 TB and whole folders as one download, in parallel chunks that resume after a dropped connection, so a multi-terabyte deliverable moves over the network instead of on a courier’s schedule. Large file delivery covers the speed in detail.
Yes. The manufacturer gets a scoped login or a protected link, and every download is written to the audit log with the user, the file, the time, and the source IP. A question about who received a revision is a lookup, and the log is retained for seven or more years.
Yes. The same project folder is reachable over SFTP, FTPS, the web, and the desktop app, so a supplier with an automated drop connects over SFTP while a client contact uses the browser, and both land in the same folder under the same permissions.
Set an expiry on the external accounts and the share links, and a retention rule on the project folder that archives or deletes the files after the window you choose. Closed projects clean themselves up, and the audit log keeps the record of what was exchanged.
No. The project folders appear as a drive in the Files.com desktop app, so an engineer saves a revision from the CAD application into the project folder the way they save anywhere else, and the outside firm sees it in their browser or SFTP client.
A scoped space per project, links for the bidder without an account, an intake for what comes back, and a record of every download. Start the 7-day free trial and send the next plan set through Files.com.
No credit card required • Free for 7 days • Live in minutes