A Traffic-Enforcement Technology Provider Eliminates Manual Delivery to a Client’s GoAnywhere MFT Server With Files.com

A traffic-enforcement technology provider has delivered automated traffic enforcement to municipalities and state agencies for decades: speed, red-light, school-zone, and work-zone camera programs, up to statewide deployments.

The work is evidentiary. Cameras and LiDAR capture violations, review staff process the images, and the resulting data goes to the government agency that runs the program, where officers validate each citation. Every enforcement program is, at bottom, a data flow between the company and a government client. And government clients decide how they receive their data. Each agency brings its own systems, its own security rules, and sometimes its own file transfer platform. The company controls what it produces. It does not control the endpoint.

One Client Would Only Collect From Its Own GoAnywhere Server

When the business changed ownership, file exchange with clients was manual and ad hoc, handled entity by entity. The sharpest case was a government client that ran its own GoAnywhere MFT server and would not collect files any other way. The company's application produced the client's data files, and then a person finished the delivery: notice the new files, retrieve them, sign in to the client's GoAnywhere platform, and place them where the client expected to find them.

That put a standing human step in the middle of a client's data flow. Deliveries waited on someone being available, the routine repeated for every batch of files, and the person doing it added nothing except transport. The condition also generalizes: any agency can mandate its own platform, and each one that does would create another routine like it.

The company could not fix this by moving the client. The server belonged to the client, government agencies choose their own tooling, and this client had chosen. Whatever replaced the manual handoff had to deliver into the client's GoAnywhere server, on the client's terms.

So the fix had a short specification. Connect outbound to an SFTP endpoint the company does not administer. Move each file the moment the application produces it, with no one watching. And repeat cleanly for the next client: separate folders, separate credentials, the same pattern. The company had already made Files.com its file exchange platform after the ownership change, so the question became whether Files.com could also carry delivery into an endpoint that belonged to somebody else.

A Remote Server Connection and a Copy Automation

It could. Using Files.com Remote Servers, the company connected the client's GoAnywhere server to its Files.com site as an outbound SFTP destination. Files.com connects to the endpoint the way any SFTP client would, so the client changed nothing: same server, same credentials, same collection process on their side.

The company's application writes finished files into a Files.com folder. A Files.com Automation triggers the moment a file is created there and copies it to the client's GoAnywhere server. A failed copy retries automatically, and every run is recorded in the automation log, so a delivery that does not complete shows up instead of waiting for someone to notice. The leg of the workflow that used to be a person is now a rule.

The same structure became the company's standard for automated client integrations: a folder per client under a dedicated transfer tree, a service account scoped to the interface jobs, and an automation that moves each client's files to wherever that client's endpoint lives.

Delivery With No One in the Loop

With the automation in production, files produced by the application now land on the client's GoAnywhere server with nobody touching them.

• The client kept its platform and its process. It collects from its own GoAnywhere server exactly as it always did. Only the company's side of the exchange changed.
• A client's platform mandate is now a configuration, not a standing task. Across the account, multiple outbound connections now run across SFTP and AS2, while the company handles a steady stream of onboarding requests for client and internal integration accounts.

The Counterparty's Endpoint Is Just Another Destination

Today, when a government client tells the company where its data has to land, the answer is a connection and an automation rather than a person. Files.com treats the client's GoAnywhere server as one more destination it delivers to, which means a counterparty's platform choice sets where the company's files land, not how much work it takes to get them there.