Filebase puts files onto IPFS, a public network used across web3 and blockchain, using the same S3 tools you already know. Behind your company login, Files.com is where you organize, encrypt, and review files before they go out to that public network. So nothing reaches IPFS until you have checked it. It works over any Filebase bucket, yours or a partner's.
Filebase puts files onto IPFS, a public network that spreads copies of your files across many machines so they stay available worldwide. The flip side: once a file is out there, no single owner controls who can reach it. Filebase is storage, not a way to manage files. Nothing decides who can touch a file, encrypts it before it goes out, keeps a record, or lets you review files before they reach the public network. Files.com adds all of that.
The bucket can be yours, or it can belong to a partner, a vendor, or a customer. Prepare and encrypt files headed for someone else's bucket, pull down files a partner published, or do both. It all stays controlled and logged on your side, so you keep a clean record of every handoff.
Behind your company login, Files.com is where you organize, encrypt, and review files before they go out onto IPFS through Filebase. IPFS is a public network for storing files. Once a file is out there, it's out there, so the review step is your last chance to catch a mistake. Files.com is the gate in front of it.
Encrypt files with GPG inside Files.com before pushing them to IPFS, so only the matching key can open them. Anyone who finds the file on the public network just sees scrambled data.
Drop-off folders collect files from outsiders, and share links give people temporary access. So every file gets reviewed and approved before it goes out to the public network.
Run on AWS, Google Cloud, Azure, or your own servers and still exchange files with the Filebase bucket a partner uses for IPFS. All Files.com needs is the keys to the bucket. You never have to become a Filebase customer.
Once a file is out on IPFS, no single owner controls who can reach it. Files.com is the control point in front of it. It decides who can touch a file, keeps a record of every action, and encrypts files before anything goes out, so you keep real control even though the storage itself is public.
People sign in to Files.com with your company login before anything goes out to IPFS: SSO, SAML, LDAP, or Active Directory. When someone leaves, you cut their access in one place, so no former employee keeps a path to IPFS you forgot to close.
Before any files go out, hand each person or partner the exact folders they need, by team, project, or path. They see what they should, and nothing else.
Every login, upload, download, and change to files headed for IPFS is logged and exportable. That is the record a public network can't give you, so you can show an auditor exactly who did what.
Files.com applies GPG encryption before files reach IPFS, so the copies out on the network can't be opened without the matching key.
Show the Filebase bucket as a Files.com folder, with every action going straight through. Use this when Files.com is where you prepare and reach files headed for IPFS. Best pointed at a folder rather than the whole bucket.
Copy files between Files.com and a Filebase bucket on a schedule, one direction or both. Good for sending prepared files out to a partner or pulling published files in.
Push files to Filebase automatically when a file arrives or a rule is met. The Filebase bucket can be where files come from, where they go, or both. Files.com treats it exactly like its own storage, so you set up the rule once and never touch it again.
Outsiders send files into a Files.com drop-off folder. Your team reviews them, encrypts them with GPG, and an automation publishes the approved files to Filebase and onto IPFS. Nothing goes public until a person has signed off on it.
Files.com encrypts files with GPG before pushing them to IPFS, so the copies out on the public network can't be opened without the matching key.
Use share links to give people limited, time-boxed access to files headed for IPFS before they go out to the public network.
You run on AWS, Google Cloud, Azure, or your own servers. A partner publishes to IPFS through their Filebase bucket, or wants you to deliver files into it. Files.com syncs with that bucket on a schedule, pulling their files in or pushing your encrypted files out. You get a full record of it all, and you never have to sign up for Filebase.
Encrypt files before they go out to IPFS, so only the matching key can open the copies on the network.
Learn MoreCollect files from outsiders for review before they go out to the public network.
Learn MorePublish to Filebase automatically when a file arrives or a rule is met.
Learn MoreLimited, time-boxed share links for access to files before they go out to IPFS.
Learn MoreMove files in and out of IPFS-ready storage over SFTP, FTP, FTPS, and WebDAV from one site.
Learn MoreEvery handoff of files headed for IPFS is recorded and exportable, the record a public network can't give you.
Learn MoreWhat buyers ask about how Files.com connects to Filebase, what it costs, and what the integration actually does.
Start a free 7-day trial. Connect your Filebase bucket, encrypt and vet content, prove the workflow on your own data. No credit card required.
No credit card required • 7-day free trial • Setup in minutes