Be The Snowflake Stage
Files.com speaks the S3 protocol, so a Snowflake external stage points straight at your site and loads with COPY INTO — no S3, Azure, or GCS bucket to stand up or pay egress on.
See The S3-Compatible APIHow Files.com Fits With Snowflake
Snowflake loads external data from a stage, and a stage can point at any S3-compatible endpoint, not only Amazon S3. Files.com exposes an S3-compatible API, so Snowflake pulls files directly from Files.com — 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. Your Snowflake external stage points at the Files.com S3-compatible endpoint, and COPY INTO loads the data straight from us — clean, current, and staged with no second copy anywhere. The same path runs in reverse for the data Snowflake unloads 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 Load
Convert CSV, JSON, XML, and EDI into the shape your load expects, and pull values out of each file to route it, before Snowflake ever reads it.
See Transform & ExtractStage Files Automatically
An Automation validates each new arrival and files it where your Snowflake stage reads it on the Files.com endpoint — on a schedule or the moment it lands.
See AutomationsFiles.com With Snowflake FAQ
Put Files.com In The File Path
Receive, transform, route, and audit every file moving to and from Snowflake — on one platform, with no server of your own to run.
No credit card required • Free for 7 days • Live in minutes