An Automotive Parts Distributor Replaces FileZilla Server Without Touching Tens of Thousands of Repair Shop PCs

A North American automotive parts distributor supplies replacement parts to independent repair businesses across the continent. Alongside parts, it sells shop-management software for those independent repair businesses.

That software is a desktop application. It runs on PCs inside thousands of independent businesses that the distributor does not own or manage, and it is built to keep itself current. Every installed copy downloads its own updates, automatically, without the shop doing anything. That means somewhere behind the product there has to be a distribution service that tens of thousands of machines can quietly reach.

For years, that service was one physical server. Replacing it would mean preserving an FTP workflow already embedded in tens of thousands of PCs without reconfiguring the installed base.

The Whole Channel Ran on One Physical Server

The distribution service behind the software was a self-hosted FTP server: a single piece of physical hardware running FileZilla Server. Every copy of the software in the field pulled its updates from it, tens of thousands of downloads in some months. A commercial product sold to thousands of businesses depended on that box for staying current, and the load was machine-to-machine at a scale self-hosted FTP on one machine was never suited to carry.

The distributor wanted the channel off hardware it owned and on a service built to carry that load.

A Replacement That Could Not Touch the Installed Base

The hard part was not finding hosted file transfer. It was that the update behavior lived inside software already shipped. The protocol and the whole access pattern were embedded in copies of the software running on tens of thousands of PCs that the distributor could not reach to reconfigure. Shops did not provision accounts or manage credentials. By design, they did not know a file transfer was happening at all.

So the replacement had to meet the shipped software where it already was. It had to speak FTP, because that was what the installed base spoke. It had to accept the access pattern the installed base already used, at tens of thousands of downloads a month, and absorb the concurrency of a release day. It had to stay invisible to the paying customer. And it had to run with no hardware behind it, because owning hardware was the problem.

The distributor selected Files.com and stood up the hosted backend.

One Endpoint, Tens of Thousands of Machines

Files.com became the distribution backbone behind the software: a hosted site that stood exactly where the old server stood. Because Files.com presented a native FTP endpoint, the update design embedded in the shipped product carried over unchanged. Installers are published to the site at each release, and every installed copy of the software pulls them down exactly as it always has.

That design is what makes the channel free to grow. A new repair shop is not a new user to create on the platform. It is one more copy of the software pointed at the same endpoint, so onboarding a shop adds no administrative work on the platform.

Terabytes a Month, Invisible to Every Shop

With Files.com carrying the channel, the distributor replaced a distribution service that lived on one physical box with one that has absorbed years of growth without re-architecture.

• Tens of thousands of PCs across thousands of businesses pull their updates from the site, terabytes a month, and no shop ever sees the platform behind it.
• At each release, most of the installed base takes the new version, and the channel carries the surge.
• The team nearly tripled its release cadence on the same channel, with no change to the distribution design.
• New businesses and PCs join the update channel with no platform provisioning or added administrative work.

A service critical to the business no longer depends on hardware anyone at the distributor owns.

Distribution Infrastructure Nobody Has to Run

Today, a shop owner who buys the software gets a product that quietly keeps itself current, and nobody at the distributor runs a server to make that true. The work that once meant owning, patching, and worrying about a physical FTP box now means publishing installers to Files.com and letting the installed base pull them down. The distributor can add shops, add PCs, and ship releases far more often without the distribution layer ever appearing on anyone's to-do list.

And they never re-architected the shipped product to get there. Files.com accepted the same embedded FTP pattern the software already spoke, at a scale one self-hosted server never could. Retiring the server did not require touching tens of thousands of PCs.