A Network Equipment Manufacturer Tracks Every Firmware Download Through Files.com Without Making Customers Log In

A network equipment manufacturer makes fiber-based networking equipment and the software that runs it. It sells predominantly through channel partners into government, education, healthcare, and hospitality networks across North America.

That model puts the people who ultimately download its software across an installed base the company reaches at arm’s length. Distributing software to those customers is standing work for the company, and the manufacturer wanted every release to leave a record of who had taken it.

Why the Manufacturer Wanted a Record of Every Download

As of mid-2024, the manufacturer ran file transfer on an in-house system it had built itself, and software distribution ran through it as a public download path that left no record to work from. For a manufacturer whose product is half software, the company wanted more from that channel: a way to connect a version to the customers who had taken it, and a way to reach each of them when an update or new release notes followed.

The obvious way to get that record was worse than going without it. The standard way to make downloads accountable is to gate them behind accounts and make every customer log in for every file. The manufacturer’s engineering leadership explicitly did not want that. The point of knowing who took a file was for the customer’s benefit, so the company could tell them when an update or new release notes existed, and a login wall would tax exactly the people the record was meant to serve.

The requirement was distribution that stayed as easy as a public download but left a real record behind it. The link had to work in any browser with no account and nothing to install. The record also had to land in the systems where the manufacturer’s customer data already lived, not in a transfer tool off to the side. The manufacturer selected Files.com to be that distribution layer.

A Branded Link in Front, an Event Feed Behind

The manufacturer put Files.com in front of software distribution using Files.com share links under its own domain. On the customer’s side, nothing is asked of them: they follow a link on the manufacturer’s own address, and the file downloads in the browser, with no account to create and nothing to install.

Files.com records each download as an event and sends it through its external events endpoint into the manufacturer’s existing customer and vendor portal. The portal is backed by a data warehouse connected to the company’s CRM and NetSuite ERP, so the file-level activity arrives in the system where it already manages customer context. The manufacturer did not have to build a new portal or move its customer data anywhere. It instrumented the distribution channel and fed the systems it already had.

Every Release Now Leaves a Record

Each release published through the Files.com channel now produces a continuing record of download activity in the portal while customers keep the same no-login browser path. The manufacturer can now see which customers took a release and tell them when the next one follows.

The Record Comes From the Channel, Not the Customer

Files.com supplies the record as a byproduct of moving the file, and the manufacturer’s own portal keeps that activity next to its existing customer data. Today, a customer pulls a release the way they would pull any public file, with a click in a browser, and the manufacturer receives the download event.

The download did not get harder. It started leaving a record.