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.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
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.
Publishing to IPFS is permanent. Once a file is on the public network, there is no pulling it back from every machine that copied it. Your team reviews and approves inside Files.com first, so the mistake gets caught while the file is still private.
Encrypt files with PGP/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.
IPFS has no logins, no permissions, and no record of who did what. Files.com puts all three in front of it, so publishing to a public network still runs under your company's rules.
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 the folders you granted, 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 manages the keys, not just the cipher. Generate or import keys, rotate them on a partner's schedule, and give different folders different keys, all in the GPG Key Manager. No scripts, no per-machine keyrings.
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.
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. 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.
Sync a folder to Filebase on a schedule so an encrypted copy of your records lives on IPFS, spread across many machines worldwide. The archive stays reachable even when your own systems aren't, and only the matching key can open it.
Send a reviewer a share link that expires on a date you set. They check the exact files headed for IPFS, and the access shuts off on its own when the review is done.
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.
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 MoreTrigger pushes to Filebase on file arrival, a schedule, or a webhook call.
Learn MoreGive outside reviewers time-boxed access to files before they go out to IPFS.
Learn MoreMove files in and out of IPFS-ready storage over SFTP, FTPS, FTP, and WebDAV from one site.
Learn MoreEvery login, upload, and handoff of files headed for IPFS is recorded and exportable.
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.”
How Files.com connects to Filebase, what you need to set it up, and what happens to files before they reach IPFS.
Yes. Files.com connects to any Filebase bucket you hold credentials for and can pull content from it or push content to it. That bucket can be your own, a partner's, a vendor's, or a customer's. The bucket does not have to be yours.
No. Many Files.com customers run on AWS, Google Cloud, Azure, or on-prem and use the Filebase integration only to exchange with a partner or vendor who standardized on Filebase for IPFS publishing. You connect with a bucket name, Access Key, and Secret; no Filebase account of your own is required.
Files.com connects to any Filebase bucket you have the keys for. Filebase puts files onto IPFS, a public network for storing files, using the same S3 tools you already know. Files.com treats the bucket like any other S3-compatible storage, so you can mount, sync, and automate against it from one site.
Yes. Files.com can encrypt files with PGP/GPG before pushing them to Filebase and onto IPFS, so only the holder of the matching key can open them. Anyone who finds the copy on the public network sees only scrambled data.
Files.com is the gate in front of IPFS. Behind your company login, you organize files, set who can reach what, keep a record of every action, collect files from outsiders through drop-off folders, and give temporary access through share links. All of it happens before anything goes out to the public network.
Files.com moves files to and from Filebase over SFTP, FTPS, FTP, WebDAV, and HTTPS, plus the web UI, Desktop App, Mobile App, and CLI. You use any of them from one Files.com site against the mounted Filebase bucket.
Yes. Files.com Automations push files to Filebase when a file arrives, on a schedule, or when another system calls a webhook. The mounted Filebase bucket works as an Automation source, destination, or both.
No. Files.com adds access controls, a complete record of every action, and PGP encryption before files go out to IPFS, so you keep real control even though the storage itself is public.
Partners deliver over SFTP, FTPS, or a browser into scoped Files.com folders. Each sender gets its own credential, every arrival is logged, and an automation routes the file onward to the bucket.
Yes. Every transfer through Files.com to or from the bucket lands in the immutable audit log, so decentralized storage still comes with a centralized record of what moved and who touched it.
Files.com file-delivery monitoring alerts you when an expected file doesn't arrive on time. You set when each feed is due, so a feed that goes quiet gets caught that day, not when a gap in the archive turns up at retrieval time.
Start a 7-day free trial. Connect a 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 • Live in minutes