NAPA TRACS Replaces FileZilla Server Without Touching 26,000 Repair Shop PCs

Genuine Parts Company is a nearly $24 billion distributor of automotive and industrial replacement parts whose NAPA Auto Parts network serves independent repair businesses across North America. Alongside parts, GPC sells NAPA TRACS, shop-management software for independent repair businesses.

TRACS is a desktop application. It runs on PCs inside thousands of independent businesses that GPC 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 26,000 PCs without reconfiguring the installed base.

The Whole Channel Ran on One Physical Server

The distribution service behind TRACS was a self-hosted FTP server: a single piece of physical hardware running FileZilla Server, administered by software architect Mike Miller. Every copy of TRACS in the field authenticated to it as the same shared service account, and that one account was generating 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 incumbent did not decline gradually. The hardware went away, and the update channel for a revenue-generating product went with it.

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, the identity model, and the whole access pattern were embedded in copies of TRACS running on tens of thousands of PCs that GPC 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 a single service identity carrying essentially all of the traffic, 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 be stood up by one architect, with no hardware behind it, because owning hardware was the problem.

Miller selected Files.com and stood up the hosted backend.

One Service Identity, Tens of Thousands of Machines

Files.com became the distribution backbone behind TRACS: 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 were published to the site at each release, and every installed copy of TRACS authenticated as a single shared service account whose credentials shipped inside the product. That one identity now carries nearly all traffic on the site.

The shared-identity design is what makes the channel free to grow. A new repair shop is not a new user to create or a credential to distribute. It is one more consumer of an identity that already exists, so onboarding a shop adds no administrative work on the platform.

“The people who buy our software do not even know this exists. It's just our software has to update itself.”

Five Terabytes a Month, Invisible to Every Shop

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

• Roughly 26,000 PCs across some 8,000 businesses pull their updates from the site, transferring about 5 TB a month, and no shop ever sees the platform behind it.
• At each release, 70 to 80 percent of the installed base takes the new version, most of it as a 700 MB server installer, 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.

The service Miller describes as "critical to our business" no longer depends on hardware anyone at GPC owns.

Distribution Infrastructure Nobody Has to Run

Today, a shop owner who buys NAPA TRACS gets a product that quietly keeps itself current, and nobody at GPC 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. GPC 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 26,000 PCs.