A Surveying Software Company Stopped Borrowing FTP Servers With a Files.com LiDAR Endpoint of Its Own

An AI surveying software company turns mobile LiDAR scans into the deliverables surveying and engineering teams actually work in: CAD base maps, asset inventories, and GIS feature layers. The company sells its platform to state departments of transportation, utilities, and the national engineering firms that serve them, automating extraction work that has traditionally taken those teams days to weeks per project.

Every one of those projects begins with someone else's data. The platform runs on point clouds and imagery captured by its customers, and its ingest pipeline accepts data from all the major scanner manufacturers precisely because the company never controls how a dataset was collected. Before the software can extract a single curb line, terabytes of raw LiDAR have to travel from a customer, a partner, or a prospect into the company's hands. File exchange is not a back-office function at the company. It is the first step of every relationship the company has.

Every Transfer Ran on Whatever the Counterparty Had

The company had no exchange infrastructure of its own. In the surveying world, FTP is the entrenched standard for moving large datasets, so every transfer ran on the counterparty's server. That meant every new relationship opened with the company asking for credentials to somebody else's FTP box. When the other side had no server to offer, the fallback was cruder: at one point, the company was shipping hard drives.

The cost landed at the worst possible moment: the start of a relationship. Customers and OEM partners would send raw data only if it required no extra steps on their side. They would not reformat exports or adopt new tooling to accommodate a vendor, so the burden of every transfer fell on the company, using whatever aging infrastructure the other party happened to run. That infrastructure was unreliable, and a multi-terabyte upload that failed partway had to be restarted from the beginning.

The company could not fix this by dictating tools to an industry. Its counterparties were national firms and public agencies with their own IT and twenty years of FTP habits, the datasets were far too large for email or consumer file sharing, and an early-stage team building perception software was not going to build and operate transfer infrastructure across dozens of outside firms.

Terabytes Inbound, With No Consistent Way to Receive Them

The volume was outgrowing the ad-hoc arrangements. An OEM partner that manufactures scanning hardware was ready to send terabytes of demo data, and its own legacy FTP server was one the company had used directly and found painful. Established customers wanted to push terabytes of raw data in new categories for the company to develop against. The company also needed to move data outbound, sending ready-to-export files to surveying teams for validation runs, without opening yet another credential negotiation.

What the fix had to do was clear. The company needed an exchange endpoint it hosted itself, speaking the FTP and SFTP the industry already uses so no counterparty had to install anything. It needed a browser path for the firms that would rather drag a project folder into a web page. It had to keep each firm's data separate from every other firm's, and it had to handle terabyte-scale uploads. The company selected Files.com to be that endpoint.

A Scoped Account and a Dedicated Folder for Every Outside Firm

The build inverted the old arrangement. Instead of asking each counterparty for access to their server, the company gave each one access to its own: a Files.com user account per outside firm, with a dedicated folder scoped so every firm sees only its own data. National engineering firms and state agencies connect over FTP or SFTP with the clients they already run. Less technical senders upload entire project folders straight from the browser, with nothing to install. The company's own team works the same files through the Files.com Desktop App.

The rollout was additive rather than a cutover. The company stood up endpoints firm by firm as relationships came online. Provisioning the next counterparty takes an administrator minutes: create the user, create the folder, send the credentials. One of the company's co-founders runs the whole operation.

Terabytes Arrived, and No One Asked for Credentials

With the Files.com endpoint in production, the company replaced borrowed servers and shipped hard drives with a single exchange point it controls.

• The OEM partner now uploads through the Files.com endpoint the company stood up for it, replacing the legacy server it had found unusable.
• Dataset exchange with national engineering firms and public agencies runs through one platform, and most of the accounts on it belong to outside firms rather than company staff. Onboarding a new firm is a user and a folder, with no negotiation over whose server and no drives in the mail.
• Volume scaled with the business: storage on Files.com more than doubled in the first year, and individual clients pull hundreds of gigabytes at a time.
• The pattern extended into the sales motion itself. Account executives now provision Files.com accounts so prospects can send real datasets and watch the platform run against their own data, and when a product launch in early 2026 brought new counterparties, they landed on the same pattern instead of requiring new infrastructure.

The Company Became the Easy Party to Send Data To

Today, a data relationship at the company starts with the company handing over a login instead of asking for one. A surveying firm points the FTP client it has used for two decades at a folder that belongs to it alone. A prospect drags a project folder into a browser. The dataset that used to arrive on a hard drive in the mail, or through a credential request to someone else's aging server, is simply there when the team needs it. In an industry that was never going to change its tooling for a vendor, the company did not ask anyone to. It hosted the endpoint on Files.com and let every counterparty keep the habits they already had, which made the company the zero-friction party in every exchange and turned the hardest part of starting a relationship into the easiest.