A Test Equipment Manufacturer Supports 20-Year Hardware Lifecycles on Files.com Without Owning a Server

An electronics test equipment manufacturer builds the systems that tell other manufacturers whether their hardware actually works: optical and electrical test systems and related controllers for customers in electronics, avionics, defense, and medical markets worldwide. The company operates as part of a larger parent, which handles the site's administrative and legal work and leaves the engineering team focused on building hardware.

That hardware creates a long obligation. The manufacturer's products ship with firmware, configuration files, and supporting software, and they stay in service for 15 to 20 years. A customer who bought a test system a decade ago may need its software today, unchanged from the day it was published. A company that ships hardware that lives that long has to be able to deliver software for just as long.

The Files Email Refuses to Carry

The software itself was the problem. Firmware images, installers, and in-house applications travel as .msi files, .exe files, and zip archives with executables inside, which is exactly what corporate mail systems block.

When email cannot carry a file, delivery needs another path, and the manufacturer wanted one path for every recipient rather than one per recipient. It also wanted a standing, company-scoped place for proprietary files exchanged under NDA, with a durable archive behind it. A support archive for 20-year hardware has to stay reachable for the life of the hardware.

A File Server With Nobody to Run One

The obvious fix, a self-hosted FTP server, was off the table twice over. The manufacturer's people build and test hardware, and nobody at the site could take on running a server as a job. And the company's own IT would not put a customer-facing box on the production network. Anything customers could reach had to be isolated from the servers that run the business.

So the requirement was specific: an FTP server that customers never have to know is an FTP server, with access separated per customer company down to individual NDA folders, hosted somewhere other than the manufacturer's network, and simple enough for engineers to run alongside their actual jobs.

The manufacturer selected Files.com to be that server.

A Portal Where Each Customer Sees Only Its Own Files

Customers reach the portal through a support link on the manufacturer's website. Behind it, the electronics and firmware engineer who runs the site built the access model out of Files.com users and groups. Each customer contact gets an account assigned to a group representing their company. Group-level permissions mean a new contact inherits exactly their company's access. When proprietary information moves under NDA, it goes into a folder that only that customer can see.

Files are organized by product model, with deprecated versions archived alongside current ones so a customer can downgrade when a situation calls for it. Most customers work in the browser; the same accounts connect over SFTP or FTPS when a customer's systems prefer a protocol.

Because Files.com hosts the whole thing, the portal meets the isolation requirement by construction. There is no path from the download site into the manufacturer's production servers, because the download site does not run on its network.

Distribution That Outlives the Products

With the portal in production, the manufacturer established a standing product-support channel for hundreds of customers, and the channel carries exactly the payloads email rejects.

• Installers, firmware, and executables reach customers through the portal. Nothing bounces off a mail filter, and every delivery goes out through the same company-scoped channel.
• A file published once stays downloadable for the 15-to-20-year life of the hardware. A customer returning years later for a file that never changed finds it where it always was.
• Adding the next customer is a user in a company group. The permission model applies itself, with no new access design per customer.

None of this added infrastructure. There is no server on the manufacturer's network, no patching cycle, and no dedicated headcount spent on file transfer. The manufacturer's engineers administer the entire archive alongside their engineering work.

Twenty Years of Support, No Server Owned

Today, honoring a 20-year support obligation at the manufacturer means keeping a folder published and a customer's group current, and a file has a home for as long as the customer's hardware does. Files.com is the file server; the manufacturer's engineers stay on the hardware.

A manufacturer whose products outlive most software platforms keeps customers supplied for the life of the hardware, without owning a server or hiring anyone to run one.