Filebase FAQ

Filebase is the world’s first object storage platform powered by decentralized storage networks. Below you can find frequently asked questions about Filebase.

We unify multiple networks under an single S3-compatible API to make decentralized storage simple, accessible, and easy to use.

How does Filebase work?

Unlike traditional cloud providers, Filebase does not operate any physical infrastructure. Instead, we maintain a cluster of application servers connected to various decentralized networks. This results in a lower overhead and capital expense due to fewer servers.

Users can upload data to Filebase using the browser-based interface or by using our S3-compatible API. 98% of traffic is served through our S3 API.

What Storage networks do you support?

The Filebase platform has had the ability to scale horizontally across multiple underlying networks since 2018, thanks to our modular design. Today Filebase supports the following Web3 Storage Networks:

If you would like to have your storage network added to Filebase, please email [email protected]

Why would someone use Filebase instead of going directly to these networks instead?

Since we started building Filebase in early 2018 and up-through today, Web3 technologies are still very difficult to use for the everyday consumer and enterprise. They require complex software, something that needs to be constantly running to ensure file health and fed with cryptocurrency. We recognized early on that an “easy onramp” was necessary for wide-scale adoption and use of these powerful technologies.

I’ve read a lot about AWS S3 Buckets leaking data - How secure is Filebase by default?

In an effort to further simplify security and access control, objects on the Filebase platform inherit the ACL of the parent bucket. For example, the GetObjectAcl and GetBucketAcl methods will function as expected, but the GetObjectAcl response will return the ACL of the bucket that the object is contained in. We believe this design decision strikes a great balance between security and usability. It also helps to prevent scenarios where a user can accidentally make an object public within a private bucket. If you need a mix of private and public objects, simply create two different buckets.

The Filebase S3 Compatible API supports HTTP/2 (which requires TLS) and data encryption at rest. Data encryption at rest is enabled by default without any additional action required by the user.

How does Filebase help my Disaster Recovery (DR) strategy?

Filebase is pioneering the concept of "native geo-redundancy" for Object Storage. Native geo-redundancy by default affords Filebase users a default level of 3x redundancy for all of their data, within one single bucket on the Filebase platform. In order to accomplish the same level of redundancy with AWS, you would need 3 regionally-distributed buckets. That means 3 times the cost too.

This makes Filebase an ideal platform for developers with valuable data or larger companies and enterprises focused on disaster recovery.

You claim that Filebase is 90% cheaper than S3. How can that be?

Filebase is the first platform that leverages multiple decentralized storage networks, and thus, does not have to build out any physical infrastructure, making the operation of our services far more efficient and cost-effective to our customers. We are taking advantage of and help to economize all of the existing unused storage capacity that is available around the world, across the decentralized storage networks we support. These networks offer native erasure coding, which results in high levels of availability, durability, and redundancy.

Does Filebase have object size limits?

Objects stored on Filebase can range in size from a minimum of 0 bytes to a maximum of 300GB. The largest object that can be uploaded in a single HTTP PUT or POST is 5GB. If you want to upload an object larger than 5GB, you will need to initiate a multipart upload via our S3 API.

For objects larger than 100 megabytes, customers should consider using the Multipart Upload capability for increased reliability.

How is storage usage calculated?

Filebase storage usage is calculated in binary gigabytes (GB), where 1GB is 2³⁰ bytes. This unit of measurement is also known as a gibibyte (GiB), defined by the International Electrotechnical Commission (IEC). Similarly, 1TB is 2⁴⁰ bytes, i.e. 1024 GBs.

How much is pricing on Filebase?

Please review our Pricing Model for more information around our current storage pricing on Filebase.

Does Filebase have a minimum monthly charge?

Yes, all paid subscriptions are charged a minimum of $5.99 per month. This pricing includes 1 TB of storage and 1 TB of bandwidth. All storage and bandwidth usage beyond that is charged a simple $0.0059 per GB.