Connect any GCS bucket as a source, a destination, or both. It can be your own, or a partner's, vendor's, or customer's. Files.com serves SFTP, FTPS, WebDAV, share links, inboxes, and automations on top, with a real UI and a full audit trail. You don't have to be a Google Cloud shop to use it.
Google Cloud Storage holds files reliably and at huge scale. But unlike AWS, Google has no SFTP product to put in front of it. Files.com sits in front of any GCS bucket you have the keys to, yours or a partner's, and adds SFTP, FTPS, WebDAV, share links, drop-off folders, automation, encryption, and a real screen people can use. Every action is logged on your side.
The bucket can be yours, or it can belong to a partner, a vendor, or a customer. Pull files out of someone else's bucket, drop files into theirs, or do both at once. Every move is controlled and logged on your side, so you keep a full record without giving anyone direct bucket access.
Run on AWS, Azure, or your own servers and still connect to a partner’s GCS bucket. All Files.com needs is the keys to the bucket. You skip standing up a Google Cloud project just to trade files with one partner.
Mount your own bucket and every action goes straight to GCS. Nothing is copied out, and your files stay in your Google region, so your data residency rules hold. When the bucket belongs to someone else, a scheduled sync moves only the files the job needs.
Serve SFTP, FTPS, FTP, and WebDAV from one Files.com site on top of the bucket. Google has no SFTP product of its own, so Files.com fills the whole gap.
Move, encrypt, and route files on a schedule or the moment they arrive, with no Cloud Functions code to build. And every Files.com event can post to Google Pub/Sub so the rest of your stack (Cloud Run, Dataflow, BigQuery) can react.
Google Cloud's own settings decide which service accounts can touch the bucket. They were never meant to manage the people and partners working with the files inside. Files.com adds that part: who can see what, a record of everything, and the same company logins your team already uses.
Hand each person or partner the exact folders they need, by team, project, or path. It all sits on top of the one service account that reaches the bucket. They see what they should and nothing else, so a partner can never browse another partner's files.
Every login, upload, download, and change is logged and exportable. That's the proof a SOC 2 review or a partner dispute asks for, without building the logging yourself.
People sign in with your company login: SSO, SAML, LDAP, or Active Directory. When someone leaves, you cut their access to the bucket in one place, so no orphaned login keeps reaching your files.
Files.com can encrypt and decrypt files automatically as they move, so sensitive data is protected before it ever goes out or gets handed off. Nobody has to remember to do it, and there’s no separate tool to run.
Show the bucket as a Files.com folder. Uploads, downloads, and deletes go straight to GCS with no copy and no delay. Use this when you want Files.com to be the place people go to reach the bucket.
Copy files between Files.com and a GCS bucket on a schedule, one direction or both. Use this when you need a copy in two places, a one-way archive, or to move files between clouds.
Kick off a Files.com Automation when a file arrives, on a timer, or when a rule is met. The GCS bucket can be where files come from, where they go, or both. Files.com treats it exactly like its own storage.
A partner drops large files, like video or design assets, into a Files.com drop-off folder, and they land in your GCS bucket right away. No emailing files around, no guessing which version is current, and no GCS access handed out.
Send finished reports from GCS as share links you can track and set to expire. Clients send signed forms back into the same spot through a drop-off folder. It all runs against the bucket, and it's all logged.
When a file shows up in the GCS folder, Files.com posts to Google Pub/Sub, which can set off a Cloud Function, a Cloud Run service, or a Dataflow job. Uploads, shares, automation runs, and transfer status are all things it can post.
You run on AWS, Azure, or your own servers, but a partner drops data into their GCS bucket, or wants you to put files into it. Files.com syncs with that bucket on a schedule, pulling their files in or pushing yours out. You get a full record of it all, and you never have to sign up for Google Cloud.
Move, copy, and sort files on a schedule or the moment they arrive. This is the work you'd otherwise keep alive with Cloud Functions and gsutil scripts.
Learn More
Send every Files.com event to a Pub/Sub topic: uploads, automation runs, transfer status, and share-link activity. Cloud Run, Dataflow, and BigQuery can react on their own.
Learn MoreEvery access, download, and permission change is recorded and exportable. It's a fuller record than the basic access logs GCS gives you.
Learn MoreLet partners and apps reach the bucket over SFTP, FTPS, FTP, and WebDAV. These are the ways they actually connect, and none of them is something GCS offers.
Learn MoreCollect files from partners and clients straight into the GCS bucket without handing out a Google account or direct access to the bucket.
Learn More
The everyday-documents side of Google. Pair it with GCS when a job spans both shared Drive files and bulk stored files.
Learn MoreApril 13–15, 2027 · Las Vegas, NV
Files.com builds deeply on Google Cloud Storage, Drive, and Workspace, so of course we’ll be on the floor at Google Cloud Next telling our File Orchestration story. The legacy MFT vendors won’t be there.
See Files.com At Google Cloud Next
What buyers ask about how Files.com connects to GCS, what it costs, and what the integration actually does.
Start a free 7-day trial. Connect your bucket, run a test transfer, prove the integration works on your workload. No credit card required.
No credit card required • 7-day free trial • Setup in minutes