A Dental Implant Manufacturer Runs Dental Lab Intake and ERP Exchange Through One Files.com Endpoint at Millions of Transactions a Day

A global dental implant manufacturer sells in dozens of countries across North America, Europe, Latin America, and Asia. Its products are patient-specific: an implant is built for one mouth, from digital files that describe that mouth.

Those files come from outside the company. Hundreds of independent dental labs scan patients, design restorations, and send the results to the manufacturer as file bundles. The company's CAD operators turn them into finished implants. The manufacturing line begins with a file transfer, and the file contains patient-identifiable data.

What began as a single small daily file grew into a governed exchange supporting dental manufacturing, ERP, banking, HR, and partner workflows, handling millions of transactions a day.

Regulated Files Needed a Posture the Company Could Defend

When the manufacturer chose its file exchange platform, anything patient-identifiable needed encryption and a security posture the company could defend.

The first workload was deliberately small: a single small data file, pushed daily by one external account, pulled by one internal account, and deleted each day. The requirements attached to it were not small. The file had to be encrypted at rest, and access had to be locked to two domain accounts signed in through the company's own Microsoft Entra ID directory. Plenty of services could have moved the file itself.

The harder requirement sat further out, because expansion past that first file was flagged from the outset. The manufacturer does not control the systems on the other end of its transfers. Dental labs run their own applications, which push files the moment a case completes, over whatever transfer protocol is built into that software. A technology partner runs its own delivery job out of Amazon S3. A fax vendor delivers over SFTP. An ERP speaks REST. Whatever sat in the middle had to accept the protocols and interfaces those systems already use, and put encryption, identity, and compliance-grade handling around every one of them.

The manufacturer selected Files.com to be that exchange point.

An Intermediary Between External Systems and Internal Ones

The platform's job at the manufacturer comes down to one line: an intermediary that passes files from external systems to internal ones. The deployment started exactly that narrowly, one file and two accounts, and grew workload by workload.

Identity came first. The company connected Entra ID to Files.com over SAML, with SCIM provisioning users and groups straight from the directory. Group membership drives both access and role, so bringing on a new platform administrator is a directory group change rather than an account someone creates by hand. Access to regulated files is governed where the company's security team already governs everything else, with no second user list to keep in sync.

Scan Bundles In, Implants Out

The lab intake is the workload that feeds the factory. When a lab completes a case in its own application, the application uploads a few files: drawings and encrypted scans of the patient's mouth, bundled per case. Hundreds of labs send transactions every day, landing on endpoints running under the company's own custom domain. The manufacturer pulls the bundles into its internal systems, where CAD operators build the implants. The labs push the way their software always has, and Files.com is the governed endpoint on the other end: encrypted at rest, under the company's own identity, and covered for HIPAA.

The Same Exchange for the ERP, the Bank Files, and the Faxes

The pattern generalized. When the manufacturer completed its Oracle Cloud ERP cutover, it put Files.com between the ERP and its banking and HR systems. The existing exchange absorbed hundreds of thousands of REST API calls a day from the ERP, along with SFTP deliveries from a cloud faxing vendor and an implant technology partner. Each counterparty could connect with what it already ran, without the company creating or vetting a separate transfer channel.

Millions of Transactions a Day Through One Exchange

The manufacturer measured the volume itself through Files.com reporting: a sustained rate of millions of transactions a day. The same reporting gives the team per-source visibility into how its data moves.

From One File a Day

Today, the company whose first request was a place to drop a single small file runs its manufacturing intake and its back office through that same exchange. A lab finishing a case starts an upload, and a CAD operator finds the bundle where internal systems expect it. When the ERP came online, the bank and HR files went where every other regulated file already goes, and nobody had to vet a new channel to carry them.

The manufacturer never ran a platform-wide file transfer program. It picked Files.com for the data it most needed to protect, and let every flow that followed land on the same governed point. Chosen once for its security footprint, the exchange became the company's standing answer to a question that used to be asked one file at a time: how regulated data gets from outside the company to the systems that need it.