An Injection Molder Moved Its FTP Hostname to Files.com Without Changing the Address Suppliers Used

A precision plastic injection molding manufacturer depends on coordinating tooling and production files with outside tooling suppliers and partner plants.

Those relationships span North America and Asia. Tool and production files move between the manufacturer and companies whose systems it does not control, across company boundaries and an ocean.

The FTP Server Every Supplier Connected To

For years, the front door for that exchange was a server the manufacturer ran itself: an internet-facing FTP server on its own infrastructure, reachable at a hostname under the company's own domain. Every external supplier and partner account lived on that machine, and so did the responsibility for it. Availability, patching, and deliberate exposure to the internet all belonged to the company's own IT organization.

That was the real condition: the manufacturer was in the internet-infrastructure business as a side effect of being in the molding business. Supplier relationships on two continents depended on one self-hosted machine staying up.

The Hostname Was the Hard Part

The server itself was ordinary. The address was not. Supplier and partner sites on two continents all connected to the same hostname, each with its own account, each with its own setup at its own end. Retiring a server like that ordinarily means standing up a replacement at a new address and asking every external party to switch over across companies and time zones. Any partner that misses the change stops moving files. That coordination cost is why self-hosted FTP servers outlive everyone's patience with them. Replacing the machine is easy. Replacing the address is not.

The manufacturer's replacement preserved those external connections. Partners could keep reaching the same hostname, while the company kept in-house control of accounts and what each account could see. The site also retained the company's own name and branding.

Files.com became the platform behind that hostname.

The Same Address, Served by Files.com

The manufacturer moved the hostname itself onto Files.com as a custom domain. The address its partners had always used now resolves to Files.com, and the transfer site behind it carries the company's own logo. Partners connect over FTP and SFTP using accounts the manufacturer issues them.

Administration stayed exactly where the company wanted it. Using Files.com user administration, the manufacturer creates an account for each supplier or partner site and gives each one its own home directory, so every external login lands in its own area and sees only its own files. That per-account scoping is what makes a single shared site safe to hand to many outside companies at once: one address for everyone, with each supplier walled off from the rest.

What no longer exists is the server. There is no machine on the company's network hosting partner file exchange, nothing for it to patch, and no self-run transfer system reachable from outside.

A Decade Without a Server to Patch

With the hostname on Files.com, the manufacturer replaced a server it had to operate with a site it only has to administer.

The manufacturer has run external file exchange on its own branded hostname since at least 2012, and that exchange runs on Files.com today. It still owns the front door: the name on it, the accounts that open it, and what each account can reach. It no longer owns the machinery behind it.

The manufacturer's decade on Files.com carries one clear lesson for anyone still running their own FTP box: what partners depend on is the address and the arrangement behind it, and the address can move. It retired its server without asking external partners to adopt a new address because the hostname moved to Files.com.