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.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Google Cloud Storage holds files reliably and at huge scale. Moving files in and out of it is the part Google leaves to you: partners on SFTP and systems that predate the cloud. Files.com sits in front of any bucket you have the keys to and does that part.
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 the folders you granted 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 partner's upload lands in the mounted 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.
A partner drops data into their GCS bucket, or wants you to put files into it, while your own stack runs somewhere else entirely. 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, using the clients and scripts they already run.
Learn MoreGive partners a branded upload page that needs no account on their side. Submissions land straight in the GCS 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
One bidirectional transfer pattern now moves files among internal systems, cloud storage, and external partners without waiting for manual logins.
Read The Story
Files.com gives lab staff a familiar folder view while genomic data stays in client-owned storage and cloud credentials remain with one owner.
Read The Story
A multi-tenant layer over Google Cloud Storage kept each bank’s environments and encryption separate while giving MANTL reusable infrastructure for new integrations.
Read The Story
The shared service had to support temporary access, persistent system exchanges, automated delivery, and the fixed-network requirements of outside partners.
Read The Story
“Files.com's strengths are simplicity, ease of use, and the cloud connectors. We don't have to invent custom infrastructure for every partner.”
“Files.com is versatile — it can manage many different situations from a single platform. We've consolidated multiple tools onto it.”
“Files.com is robust and scales to a large enterprise. We get multiple files per minute, per second — and we're a 24/7 organization, so everything has to always be up.”
How Files.com connects to a GCS bucket, yours or a partner’s, what it costs, and what the integration actually does.
Yes. Files.com connects to any Google Cloud Storage bucket you hold credentials for, your own or a partner's, vendor's, or customer's, and can pull files from it or push files to it. The bucket does not have to live in your Google Cloud project.
No. Many Files.com customers run on AWS, Azure, or on-prem and use the GCS integration only to exchange with a partner or vendor who standardized on Google Cloud. You connect with a service-account key or HMAC keys to the bucket; no Google Cloud footprint of your own is required.
No. Google Drive and Google Cloud Storage are different products, and Files.com connects to each separately. Drive is for everyday documents people open and share. Google Cloud Storage is built to hold huge amounts of data for apps, backups, and media.
Files.com supports three authentication methods for Google Cloud Storage: a JSON service-account key, HMAC keys for the S3-compatible XML API, or an OAuth connection approved through Google's sign-in flow. The service-account key is the default for most deployments. OAuth is tied to one person's Google account, so keep it for cases where keys aren't an option.
Yes. You can give Files.com read-only access, full access, or write-only access. With write-only, Files.com can drop files in but can't read them back, change them, or delete them. That's useful when you want a one-way archive that nobody can tamper with.
No. A Files.com Remote Server Mount passes every operation straight through to the GCS bucket in your chosen region in real time, and nothing is copied out. If you’d rather Files.com keep a copy, use a Sync and choose the destination: backup, a faster-access tier, or the primary store. Whether the data lives in GCS, on Files.com, or both is your call.
Yes. The full Files.com notification surface can publish to Google Pub/Sub, including uploads, downloads, shares, deletes, automation runs, and transfer status. From there it feeds downstream Cloud Functions, Cloud Run, Dataflow, BigQuery, or a SIEM.
Files.com serves SFTP, FTPS, FTP, and WebDAV from one site against the mounted bucket, plus the web UI, desktop and mobile apps, and CLI. Google ships no native managed-SFTP product of its own.
No. The Google Cloud Storage integration is included in every Files.com plan. The only Google-side costs are GCS storage and any data transfer your workload generates.
Files.com mounts the bucket in place; the data stays in Google Cloud and every protocol, automation, and permission works against it there. When the job is a one-time move of the contents of the bucket to S3, Azure Blob, or a flat-rate object store, that is what Mover, the one-time migration tool from Files.com, is for: a free dry run counts the objects and prices the move, including the egress, before anything leaves the bucket.
Connect your bucket, run a test transfer, and prove the integration on your workload.
No credit card required • 7-day free trial • Live in minutes