B2 is cheap storage, but a partner can't log in over SFTP, you can't hand someone a download link, and you can't see who did what. Files.com adds all of that on top of any B2 bucket, yours or a partner's. You move files to cheap storage and still send, receive, and share them. You don't even have to run a Backblaze account.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Teams pick B2 for one reason above all: it's cheap, and it works with S3 tools. The catch is that cheap storage is harder to use. B2 has no SFTP, no way to set partners up, no automation, and no record of who did what. Files.com is what makes the cheap bucket usable. It adds exactly the connections, automation, sharing, and controls B2 leaves out.
Move files into your B2 bucket on a schedule, and Files.com keeps serving them over SFTP, FTPS, share links, and automation. So you get the access B2 doesn’t give you, on storage that costs far less than where the files came from.
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. It's all controlled and logged on your side.
Drop-off folders, share links, encryption, automation, and every transfer protocol run on top of the B2 bucket. These are all the things B2 doesn't do on its own, and the files never move anywhere.
SFTP, FTPS, FTP, and WebDAV all reach the B2 bucket from one Files.com site, plus the web app, desktop and mobile apps, and command line.
Move, encrypt, and route files between B2 and anywhere else, on a schedule or the moment a partner's upload lands. Partner intake, archiving, and delivery all run on their own, with no scheduled script to keep alive.
Backblaze hands out API keys, not logins for people. It has no way 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. They see the folders you granted, and nothing else.
Every login, upload, download, and change is logged and exportable. That's the proof a SOC 2 review or a partner dispute asks for, and you don't build 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.
Files.com can encrypt and decrypt files automatically as they move, so sensitive data is protected before it's stored or shared. Nobody has to remember to do it.
Show the B2 bucket as a Files.com folder. Uploads, downloads, and deletes all go straight to B2 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 B2 bucket on a schedule, in one direction or both. Good for archiving, keeping a copy in two places, or moving pricey data down into cheap long-term storage.
Kick off a Files.com Automation when an upload lands, on a timer, or when a rule is met. The B2 bucket can be where files come from, where they go, or both. Files.com treats it exactly like its own storage.
A scheduled Automation pulls files out of SharePoint or a big-cloud bucket and writes them into B2, where holding them costs a fraction as much. Files.com then serves those files over SFTP, FTPS, and share links. So moving to cheaper storage doesn't cost the team the access it had before.
Partners send files over SFTP or FTPS, they land in the B2 bucket, and an automation checks and routes them. Partner file exchange on budget storage, with nothing for your partners to install.
Send large files stored in B2 as share links you can set to expire and limit. No one gets direct B2 access, and every download is logged.
Your own files live on S3, Azure, Google Cloud, or your own servers. A partner drops data into their B2 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 open a Backblaze account.
Schedule and trigger file moves to and from B2. This is the part that runs the move-to-cheap-storage and partner-intake work.
Learn MoreCollect files from outsiders straight into the B2 bucket, with no Backblaze access handed out.
Learn MoreEncrypt and decrypt files automatically as they move on and off the bucket, before they're stored or shared.
Learn MoreLet partners and apps reach the bucket over SFTP, FTPS, FTP, and WebDAV. These are the ways they actually connect, and B2 offers none of them.
Learn MoreEvery access, download, and permission change is recorded and exportable. B2 keeps nothing like it on its own.
Learn More“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.”
What you’ll want to know before putting Files.com in front of a B2 bucket, from whose bucket it can be to what it costs.
Yes. Files.com connects to any Backblaze B2 bucket you hold credentials for, and can pull files from it or push files to it. The bucket can be your own, a partner's, a vendor's, or a customer's. It does not have to live in your Backblaze account.
No. Files.com connects to the bucket with an Access Key and Secret Key from Backblaze's S3 support, so no Backblaze account of your own is required. Your own data can live on S3, Azure, Google Cloud, or on-prem. The common pattern is exchanging files with a partner or vendor who keeps its data in Backblaze.
No, not by default. A Files.com Remote Server Mount treats the bucket as a live folder, and operations pass through in real time with nothing copied out. If you’d rather Files.com keep a copy, for backup, a faster tier, or as the primary store, use a Sync and choose the destination. Files.com has its own high-performance storage, so where the data lives is your call.
Files.com serves a mounted B2 bucket over SFTP, FTPS, FTP, and WebDAV, plus the web UI, desktop and mobile apps, and CLI, all from one site.
Yes. A folder mounted to a B2 bucket works as an Automation source, destination, or both, the same as native Files.com storage.
No. The Backblaze B2 integration is maintained by the Files.com team and included in your subscription. The only Backblaze-side costs are B2 storage and any transfer your workload generates.
Partners deliver files over SFTP, FTPS, or a browser upload into scoped Files.com folders mounted on the B2 bucket. Each partner gets its own Files.com credential, never a Backblaze key, and every arrival is logged.
Yes. Files.com runs encryption and decryption as folder settings, with keys held in the GPG Key Manager. Inbound files can decrypt automatically as they land in B2, and outbound files encrypt under each recipient's key before they leave, with no desktop tooling on anyone's machine.
Files.com delivery monitoring knows the window each feed is expected in and alerts when a window closes without files. An upstream failure becomes a same-day alert instead of a gap you discover at restore time.
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