A Public-Sector Software Vendor Replaced Its Self-Hosted FTP Server Without Disrupting Housing Authorities’ Database Exchange

A North American software vendor builds enterprise software for public housing authorities.

That software is database-backed. When something goes wrong at a housing authority, the vendor's developers often need the authority's actual database to diagnose it. Those files are too large for email. So the vendor has always needed a standing channel where clients send databases in, and where support sends release files and targeted fixes back out based on what the developers find.

The FTP Server the Vendor No Longer Wanted to Run

For years, that channel was an FTP site the vendor hosted itself. The server held clients' data and had to be run, patched, and administered by a company whose actual business is housing software. Every client needed its own credentials. Every troubleshooting case and every release delivery depended on the server being up. The vendor was operating file transfer infrastructure so that its developers could do their real job: pull a client's database apart and ship the fix.

The server could not simply be switched off. The channel was customer-facing and continuous. Clients uploaded databases whenever a case demanded it, and they expected updates back through the same path. The channel also carried a structural requirement that made a casual replacement risky: every client had to be sealed off from every other client, while the vendor's own staff needed to work across a division's entire client population.

The vendor decided it no longer wanted to support an FTP site. Whatever replaced it had to support the protocols and desktop clients customers already used. It had to root each client in a space of its own. It had to give internal teams broad access without letting the folder structure drift. And it had to take on new client accounts programmatically as the client population grew.

The vendor selected Files.com to take over the channel.

A Folder Per Client, One Locked Structure

Files.com became the standing exchange between the vendor and its clients: hosted by Files.com, structured by the vendor, and accessible through the familiar protocols and tools used by the people on both ends.

The vendor built the site as a folder per client under each division. Each client user was rooted in its own folder, while internal teams could work across every client folder in their division. Group and folder permissions kept authorities isolated from one another and locked the division-level structure so it could not drift as accounts grew. Housing authorities could continue connecting with the same protocols and desktop clients, FileZilla among them, without changing their workflow.

For years, the vendor has created new client users with a PowerShell script running against the Files.com REST API. Onboarding a client stopped being administrative work: the account is created by the script and takes its place in a structure that isolates it by design.

Out of the Infrastructure Business

With Files.com carrying the channel, the vendor replaced a server it had to operate with a service it only had to structure. The change shows up in what nobody does anymore.

• There is nothing left to host. The self-hosted FTP server is gone, and with it the patching, the uptime watch, and the work of running a server that holds client data.
• Clients did not have to change their workflow. They connect with the same protocols and the same desktop clients, and the rhythm of databases in and releases out carried straight over.
• Adding a client costs a script run, not a project. Over its life, the channel has carried hundreds of client accounts, each isolated in its own folder from the day it is created.
• The security reporting the vendor's auditors ask for comes straight from Files.com. By the company's own account, that is why it has never needed to evaluate an alternative.

The vendor's head of technology tells peer companies, unprompted, that the company runs on Files.com. The FTP server was never the point. The exchange it carried was. Files.com let the vendor retire the one and keep the other.