Landis+Gyr Automated File Transfers With a Files.com Hub for Google Cloud Storage and Logistics Partners

Landis+Gyr has been metering electricity since 1896. The Swiss energy technology company builds smart meters, grid-edge sensors, and the metering and data-management software behind them, and more than 3,500 electric, gas, and water utilities in over 30 countries run on its equipment.

A meter is a physical product. It is built through contract manufacturers, moved by third-party logistics providers, and delivered into utility territories, and the systems that manage each step belong to different companies. The data that keeps that chain running—the shipment records, orders, and system exports—travels between those systems as files. For Landis+Gyr, file exchange is not an office convenience. It is what connects its internal servers, its Google Cloud storage, its logistics providers, and its customers.

When Every Transfer Needed Its Own Routine

Some of that exchange depended on manual logins and traditional file sharing. A file moved when someone signed in and moved it, making the cadence of the flow dependent on human availability. Each counterparty also had its own routine. For a supply chain that runs on files, those manual steps sat beneath operational workflows.

The condition persisted because no single fix fit all the endpoints. Internal servers exchanged files over SFTP. Logistics counterparties ran their own servers and automated processing. The storage backend was a Google Cloud bucket with an API of its own. Landis+Gyr could not redesign the systems at partner sites, and the endpoints did not share an interface. Handled point to point, every pairing becomes its own mechanism: another credential, another transfer job, another routine to maintain.

What the company needed was one layer that could sit in the middle of all of it. It had to speak SFTP, because that is what the internal servers and partners already spoke. It had to authenticate machines rather than people, with service accounts and keys instead of someone’s login. It had to move files the moment they arrived or on a fixed cycle, not when someone got around to them. And it had to read and write Google Cloud Storage directly. Landis+Gyr selected Files.com to be that layer.

SFTP Service Accounts, Upload-Triggered Automations, and Two-Way Cloud Sync

On Files.com, Landis+Gyr built a programmatic hub. Every participating system connects to the platform, and the platform does the moving.

Machine access came first. Internal systems exchanged files with Files.com over SFTP under dedicated service accounts with public-key authentication, so no password and no person sat in the transfer path. Scheduled runs every 10 to 15 minutes carried files in both directions, from internal servers up to the platform and from the platform back down.

The cloud side was event-driven. Using Files.com Automations, a file uploaded into the relevant folder structure was copied into a Google Cloud Storage bucket the moment it landed. A two-way Remote Server Sync kept platform folders and the bucket matched.

The partner side ran on the same hub. Customer shipment data synced in from an external SFTP server on a schedule, with no one fetching it. Third-party logistics exchanges ran through structured inbound and outbound folders, with files collected automatically for processing.

The infrastructure team built all of it in-house, working from the Files.com API and documentation.

“Your documentation site is amazing compared to most companies.”

One Pattern for Each New Flow

With the workflows in production, Landis+Gyr reduced human-gated, per-connection handling through a repeatable synchronization pattern. Files moved in both directions on scheduled cycles, cloud-bound files reached Google Cloud Storage as soon as they arrived on the platform, and shipment data flowed in without being fetched by hand.

Each new flow was added to the same hub instead of becoming its own mechanism. Cloud sync, logistics folder trees, and shipment-data feeds came onto the platform one after another between 2022 and 2024.

From a Task Someone Did to Infrastructure That Runs

For the workflows connected through the hub, the consequence is simple. Today, moving a file at Landis+Gyr is not a job on anyone’s list. A shipment record, a system export, or a cloud-bound file is picked up within minutes of existing and delivered where the next system expects it. Files.com reduced the manual logins and traditional file-sharing methods behind those movements.

What Landis+Gyr built is not a portal for sharing files. It consolidated system-to-system file movement across its own servers, its cloud storage, and companies it does not control onto one governed hub, and Files.com is what runs it.