Be The Source Databricks Reads
Files.com speaks the S3 protocol, so a Databricks cluster reads straight from your site over Auto Loader — no S3, ADLS, or GCS bucket to stand up or pay egress on.
See The S3-Compatible APIHow Files.com Fits With Databricks
Databricks reads files through the S3 protocol, and that protocol does not have to point at Amazon S3. Files.com exposes an S3-compatible API, so a Databricks cluster — with the S3 endpoint set to your Files.com site — reads files directly from us, and Auto Loader picks up new arrivals as they land. There is no hyperscaler bucket to provision, sync into, or pay egress on.
Partners and upstream systems send files to your Files.com site over SFTP, FTPS, or HTTPS; an Automation validates each one, normalizes the format, and files it where it belongs. Auto Loader, pointed at the Files.com S3-compatible endpoint, streams those files into your tables — clean, current, and with no second copy anywhere. The same path runs in reverse for the results Databricks writes back out to partners.
What You Would Use
Receive Files Over Every Protocol
Partners and systems send to your Files.com site over SFTP, FTPS, FTP, or HTTPS. One endpoint, one set of credentials, full audit on every transfer.
See File TransferNormalize Before Ingest
Convert CSV, JSON, XML, and EDI into the shape your tables expect, and pull values out of each file to route it, before Auto Loader ever reads it.
See Transform & ExtractStage Files Automatically
An Automation validates each new arrival and files it where Auto Loader reads it on the Files.com endpoint — on a schedule or the moment it lands.
See AutomationsFiles.com With Databricks FAQ
Put Files.com In The File Path
Receive, transform, route, and audit every file moving to and from Databricks — on one platform, with no server of your own to run.
No credit card required • Free for 7 days • Live in minutes