Files.com stands up a branded, self-service portal where every new trading partner comes online in minutes, whether that partner is a vendor, supplier, payor, lab, affiliate, or customer. They land with the right directional folders, permissions, protocols, and audit already wired up. The partner self-onboards through your own domain and lands in a workspace isolated from every other partner.
Legacy MFT runs partner onboarding as a manual, multi-step process for every partner. A custom-built portal makes your engineers maintain the code forever. Files.com runs it as a standard workflow that scales from five partners to five thousand, so onboarding stays routine no matter how big the roster gets. Every transfer is governed and audited from the first file.
A new partner signs themselves up behind a controlled wall. They land in folders already set up right, connect however they already work, and are logged from the very first transfer.
Each partner gets its own Partner Workspace, with its own users, folders, and logins, that the partner runs itself. Setting up the partner’s people stops being a job your team does by hand.
Incoming and outgoing folders only allow one direction. A partner reads from the incoming folder but can’t write to it, and uploads to the outgoing folder but can’t read or delete from it. That’s enforced automatically, so an admin doesn’t have to get it right by hand for partner number one hundred.
SFTP, FTPS, FTP, WebDAV, or AS2 for the EDI trading networks that require it. The partner connects the way they already do, with nothing on either side to set up or patch.
Every partner’s logins, uploads, downloads, and permission changes are logged from the moment they connect. There is nothing to turn on and nothing to configure per partner: the first partner and the five hundredth are governed the same way.
The portal is built from things the platform already does, combined for onboarding partners.
Each partner gets its own workspace, walled off from every other partner on every connection method: web, desktop, SFTP, FTPS, WebDAV, and the REST API. There is no way for one partner to reach another’s data. Someone on your team owns each relationship, and the partner manages its own users. You can create workspaces in bulk through the admin screen or the API, so a whole roster moving off old MFT comes online at once instead of one ticket at a time.
A branded Inbox is the front door. A new partner drops in their details and first documents through a drag-and-drop or embedded form, saved as clean, structured fields, without making an account first. The submission goes to the right person on your team and starts the setup. A partner goes from first contact to up-and-running with little hands-on work.
Files.com is a fully managed cloud SFTP, FTPS, and FTP server, with per-user folders and two-factor login at the connection level. For trading networks that require AS2, it’s a standards-compliant (RFC 4130) AS2 endpoint with managed certificates, automatic delivery receipts, and routing per partner. You rotate certificates in the interface, not by hand in connection scripts.
Partners land on your own domain with your logo, colors, and words. Login pages, upload pages, and the emails that go out all carry your brand. The portal feels like your relationship with the partner, which matters when you’re asking them to run business-critical files through it.
“Simplicity, reliability, and speed of use. The uptime alone has been worth it — we've barely had a downtime issue.”
“Files.com is versatile — it can manage many different situations from a single platform. We've consolidated multiple tools onto it.”
Real companies. Real file flows. Real results.
A team setting up partner onboarding is usually choosing between legacy MFT and a portal their own engineers build and own. Files.com replaces both.
On IBM Sterling, GoAnywhere, MOVEit, or Axway, onboarding a partner is a long list of manual steps. You create the account, build the folders, set the one-way permissions, exchange certificates, wire up the routing, and write it down for the audit. You do every step by hand for every partner, on a legacy platform you also patch and maintain. Files.com does the whole list as a standard, self-service flow.
A home-built partner portal means your own engineers write and own the onboarding, permission, and routing code forever. It costs a lot up front, and the maintenance never ends. Building your own only pays off when a partner relationship truly needs custom app logic beyond moving files, which is rare and expensive. For the everyday job that drives most of the cost, Files.com does it without the build and without the never-ending upkeep.
Onboarding a partner on Files.com is a standard, self-service routine. The wall between partners, the one-way folders, the protocols, and the audit are already built in. On legacy MFT, the same job is manual setup, partner after partner. On a portal you build yourself, it’s code you maintain forever.
Files.com publishes its pricing, so the number is on the page before you ask. The transfer protocols are included on every plan, not priced as add-on modules. When you’re replacing a legacy MFT platform and show up with a competing quote, Files.com will match or beat it.
The control a partner-exchange portal needs is built in. A vendor security questionnaire’s questions are answered before they’re asked.
Every partner action lands in an audit log no one can edit: every login, upload, download, key change, and permission change. The log is kept for 7+ years and exportable to your SIEM. AES-256 at rest, TLS in transit, and an A+ rating on Qualys SSL Labs.
SOC 2 Type II, PCI DSS, and CSA STAR, with a HIPAA BAA and GDPR DPA available. Used in production by banks, healthcare payors, and other regulated industries that exchange with regulated partners.
SSO and SAML against Microsoft Entra ID, Okta, Active Directory, Google, OneLogin, and Auth0, with SCIM provisioning, nine permission levels, IP allowlisting, and 2FA enforced down to the protocol layer.
Standing up the portal means wiring up workspaces, intake, protocols, and AS2 certificates. That’s the kind of work you want a real engineer on the other end of.
The people who answer the phone are engineers who know the platform, not a tier-one queue reading a script. When a partner connection or an AS2 certificate misbehaves, you reach someone who can fix it.
Customer Engineering stands up partner workspaces, intake forms, protocols, and routing with you. Most teams are live within five business days, and strategic enterprise deployments get our onboarding people embedded as forward deployed engineers.
Thorough docs, a fully documented REST API, and SDKs across major languages. That’s enough to wire partner provisioning into the systems you already run and bring a whole roster online at once.
The partner portal is the most common job on Files.com, and it shows up the same way at a manufacturer with forty suppliers and a bank with four hundred counterparties.
Each vendor, client, or agency gets its own login rooted in its own folder. Nobody sees another partner’s files, and revoking one partner touches nothing else.
A partner’s nightly script and a partner’s finance clerk with a browser land in the same folder, under the same rules, with the same record. The exchange does not care which path a file took.
A custom domain carries two dedicated IP addresses, so a counterparty whose firewall allow-lists your endpoint has a fixed address to allow, and one whose server you push to sees a fixed source.
Employees sign in through single sign-on and are provisioned from the directory. External partners get Files.com credentials, expiring accounts, and two-factor authentication, side by side on one site.
To clear Porsche AG's hosting rules, the channel combined federated identity, Porsche branding, and Canadian data residency for workflows across the business.
Read The Story
Files.com synchronized external-facing folders with SharePoint, giving vendors and auditors governed access while employees stayed in Microsoft 365.
Read The Story
What began as scoped SFTP access for roughly 20 accounts survived formal scrutiny and two identity migrations without becoming a standalone file-transfer operation.
Read The Story
Files.com let outside inspectors work in Spencer’s existing macro-enabled QA workbooks while named accounts, scoped folders, and activity logs preserved control.
Read The Story
What EDI and B2B-operations teams ask most when standing up a trading-partner portal on Files.com.
On Files.com, a partner onboarding portal is a branded, self-service surface where a new trading partner comes online with the right folders, permissions, protocols, and audit already in place. The partner can be a vendor, supplier, payor, lab, affiliate, or customer. Each partner gets its own isolated Partner Workspace with directional incoming and outgoing folders, connects over the protocol they already use, and is governed from the first transfer. There is no manual, multi-step provisioning of the kind legacy MFT runs by hand for every partner.
On Files.com, a new partner self-onboards through a branded intake Inbox on your own domain, submitting their details and first documents without needing an account. That routes to the right internal owner and provisions a Partner Workspace: an isolated tenancy with its own users, incoming and outgoing folders, and credentials. The partner administers its own people through delegated access, connects over the protocols it already runs, and every action is recorded. Onboarding becomes a standard workflow you repeat at scale, not a project you run a hundred times.
Each Partner Workspace on Files.com is isolated across every connection method: web, desktop, SFTP, FTPS, WebDAV, and the REST API. There is no protocol path from one partner into another’s data. Within a workspace, incoming and outgoing folders carry directional permissions: a partner reads from the incoming folder but cannot write to it, and uploads to the outgoing folder but cannot read or delete from it. The one-way permissions are enforced automatically and cannot be misconfigured. They are not per-folder settings an admin sets by hand for each partner. Nine permission levels cover the finer cases.
Files.com is a fully managed cloud SFTP, FTPS, and FTP server, so a partner who only speaks SFTP connects with nothing to provision on either side. EDI trading networks like retail vendors, claims clearinghouses, and supply-chain partners often mandate AS2. For those, Files.com is an RFC 4130 AS2 endpoint with managed certificates and automatic MDN receipts. Files.com transports AS2 byte-for-byte: the file your partner receives is identical to the file you sent. When the EDI itself needs translating, TransformScript parses and writes X12 and EDIFACT natively on the platform.
The portal carries your brand, not Files.com’s: partners land under your own custom domain with your logo, brand colors, and copy. Login pages, inbox upload pages, and outbound email all carry your identity, so the partner experiences the portal as your relationship with them. Some partner segments need hard separation below site-wide settings, like their own region, security policy, or branding. For those, Child Sites provide full site-level isolation under one parent, governed centrally. Reselling the platform as a service to others is a separate commercial arrangement. Talk to our team about it.
A single partner comes online on Files.com in minutes, because there is nothing to provision. Create the Partner Workspace, set the directional folders, and hand the partner their endpoint and credentials. A whole roster migrating off legacy MFT comes online at once: Partner Workspaces bulk-create through the admin UI or the REST API, so a hundred partners do not mean a hundred tickets.
A file landing in a partner folder is a first-class automation trigger on Files.com. The moment an upload completes end-to-end, Files.com can route the file to a downstream system, run PGP encryption, send a notification, or push it onward. Events fire only on completed uploads, so a partial file never triggers a workflow prematurely.
Files.com is SOC 2 Type II, PCI DSS, and CSA STAR certified, with a HIPAA BAA and GDPR DPA available, AES-256 at rest, and TLS in transit. Files.com has run as a managed service for 15+ years with zero breaches. Every partner action lands in an immutable audit log, and you choose which of eight storage and compute zones the data sits in. Files.com publishes its current attestations.
Files.com publishes its pricing publicly, and the transfer protocols are included on every plan rather than priced as per-protocol surcharges: SFTP, FTPS, FTP, and WebDAV. AS2 is available on the Power plan and above. The pricing page shows tiers and overages before you ask for a number. When you are replacing a legacy MFT platform and arrive with a competing quote, Files.com will match or beat it.
Create a user per partner on your Files.com site, root it in the partner’s own folder, and hand them the address under your custom domain. Files.com hosts the endpoint, the partner connects over SFTP, FTPS, or the browser, and their permissions stop at the folder’s edge. There is no server for you to run, and adding the next partner is the same three steps.
Yes. Mount the vendor’s SFTP server as a folder on your Files.com site, with the vendor’s credential stored once in the credential manager. Your staff reach the vendor’s files through their own Files.com logins, every action is attributed to the person who took it, and nobody holds the shared password.
Yes. A Files.com custom domain includes two dedicated IP addresses for inbound and outbound connections, so a partner that allow-lists your endpoint has fixed addresses to allow. Enterprise sites can route their own public IP ranges through Files.com and keep the allow-lists partners already hold.
A branded, self-service portal where every trading partner comes online with the right folders, permissions, protocols, and audit already wired up, governed from the first file. Bring a partner online on a real workload during the 7-day free trial.
No credit card required • Free for 7 days • Live in minutes
