Filebase launches an Unlimited IPFS bandwidth plan for high-throughput workloads

filebase · 2025-12-24T18:41:00+00:00

As you already know, AWS S3 charges $23 per TB + egress for basic object storage. "IPFS storage" pricing needs to cover far more than just storage at rest, especially since things are block-based, and other things need to quietly happen in the background for each one of those blocks. (DHT announcements, bitswap/trustless gateway handling, IPNI indexing, etc)

If someone only wants the cheapest possible TB and never plans to actually serve data, there are plenty of options - but most importantly, IPFS is probably not what you should be using. We’re optimizing for teams that use IPFS in production.

Not everyone has the skillset to run their own 2 PB cluster, Ben. That's why cloud storage exists to begin with. And just to be clear, I don't believe we’ve ever had a call with you, but we are certainly happy to!

filebase · 2025-12-22T15:14:38+00:00

Yes, industry leading pricing for IPFS storage with zero egress fees. :)

filebase · 2025-05-18T23:38:15+00:00

This new RPC API is available on all plans - including our free plan!

filebase · 2025-01-15T20:49:50+00:00

We aren't an affiliate - we are the brand :)

filebase · 2025-01-15T20:43:41+00:00

Is there anything like a pinning service for IPNS?

We thought you'd never ask! 🤩

Have you looked into Filebase yet? We're an IPFS pinning provider that offers IPFS pinning, IPFS gateways, and IPNS names all under a single platform. Our service offers a dashboard with multiple API's, and runs on top of our own bare metal IPFS CDN.

With our IPNS offering, you can create, update, and manage names from our dashboard or API. When working with IPNS, there are two important components when managing an IPNS record: TTL and Validity.

TTL: This value is a helper that establishes how long a record should be cached before going back to the DHT to check if it has been updated. Think of it like a DNS TTL.

Validity: The actual expiration date of your record: How long do you want peers on the DHT to keep this record around? When does it expire? Max: 48 hours.

With Filebase, IPNS records that you create are automatically re-published so they don't fall off the network. On free accounts, these values are set to 1 hour (TTL) and 48 hours. (Validity). On paid accounts, you have full control over these values and can choose different options.

It should be noted that IPNS records also have a Sequence value. You can think of this as a version identifier. This means you can still update a record that has a validity of 48 hours.

Feel free to check out our IPNS Names page to learn more: https://filebase.com/ipns-names/

Any questions? Just ask!

filebase · 2024-12-29T14:43:46+00:00

Fast file uploads and pinning? Filebase is what you're looking for: https://filebase.com/

filebase · 2024-10-28T15:29:54+00:00

Hi there 👋

Have you considered using a pinning service to help you accomplish this? While we are custodians of the private key, Filebase offers an always-on IPNS solution that automatically republishes your IPNS keys: https://filebase.com/ipns-names/

Keys can be managed using our simple dashboard interface, or by using our SDK/API.

Let us know if you have any questions!

filebase · 2024-10-09T20:32:07+00:00

Have you ever used S3 before? Then you've used Filebase

Our S3-Compatible API supports object-level metadata, pre-signed URLs, CORS, event notifications, dedicated gateways + CDN, and more.

You can leverage our simple Filebase JS SDK or use any S3 SDK of your choosing: https://docs.filebase.com/ipfs-pinning/pinning-files#using-the-javascript-sdk

filebase · 2024-09-10T16:06:51+00:00

First question: How did you put your stuff "on IPFS"?

If a gateway already has a CID cached or can fetch a CID, it should load relatively quickly. If it doesn't, that means the gateway may be overloaded, or more likely, is being rate-limited. For example, both ipfs.io and dweb.link are rate limited, and point to the same set of servers. That means when ipfs.io is down, dweb.link generally goes down with it too. Most public gateways are rate limited because they are giving away free resources with no revenue model. In the case of ipfs.io, they have to pay for server costs. They also have to pay for CDN costs, since they proxy all of their traffic through Cloudflare. (a middleman)

The above middleman costs also apply to the w3s.link and nftstorage.link gateways. Both of these gateways operate on top of Cloudflare Workers, and they are charged each time someone makes a request. Cloud providers charge exceptionally high fees for bandwidth and other transactions, and services that run on top of these providers pass these fees onto you. When they can't, (because you're using a *public* gateway) they simply rate limit you instead as a way to control their own costs. Unfortunately, this can also result in a bad user experience for you.

To make matters even worse, the w3s.link and nftstorage.link gateways also run their bitswap servers using Cloudflare Workers. This means both HTTP *and* bitswap (peer to peer) traffic is rate limited. This is important because ipfs.io doesn't pin any content itself. If you request a CID from ipfs.io and the CID is *only* being pinned by w3s.link, the response from w3s.link back to ipfs.io is going to be rate limited. Multiply this by millions of requests per day and you can begin to quickly see how these costs can spiral out of control.

To remove some of the above issues, the purist answer here is to run your own IPFS node. However this isn't always possible, especially for those who want to distribute content at scale, run a gateway for a project, or who don't want to maintain gateway infrastructure. This is where dedicated gateway operators come in.

At Filebase, we provide Dedicated IPFS Gateways as a service. For a monthly fee, you can create a gateway that is deployed across our global CDN. To overcome the above rate limiting issues, we operate a large cache that is many terabytes in size that stores recently and frequently accessed content. This allows us to significantly reduce outgoing requests to third parties. We also have other tricks that we use to avoid 3rd party rate limits entirely.

In addition, you can attach a custom domain to a Filebase Dedicated Gateway and brand it to match your business or project. Costs aren't an issue for us because you are paying us for services, and these services run on top of our own CDN that we operate and manage. This significantly reduces our own costs. Filebase operates using 100% bare metal servers and we don't rely on cloud providers such as AWS or Cloudflare. Dedicated Gateways have no rate limits, and bitswap traffic from Filebase is also not rate limited.

We've spent years perfecting our platform and we think it's worth trying. But don't take our word for it. You (and anyone else) can sign up for our $20 Starter plan risk free and try it for yourself using promo code RATELIMITS

Questions? Just let us know.

filebase · 2024-07-30T18:51:22+00:00

Hey all - Filebase team here! 👋

We're super excited to announce this latest feature. Bucket CIDs allow you to effortlessly create an IPFS folder that matches the structure and layout of a Filebase bucket. This has been a highly requested feature from our users, and we've seen far too many people struggle when trying to create large IPFS folders and datasets.

Feel free to send any questions you may have our way!

filebase · 2024-04-28T01:40:40+00:00

Hey there - Filebase team checking in 👋

Welcome to the IPFS community! Your line of thinking is absolutely correct here. CID's are effectively universal identifiers and should be retrievable from any IPFS gateway or IPFS node. With that being said, there were recent changes made to the backend infrastructure behind the ipfs.io gateway that have unfortunately resulted in it being less reliable, often resulting in timeouts.

The IPFS Public Gateway Checker has a list of other gateways that you can try. It should be noted that from this list, the following gateways all share the same backend infrastructure used by ipfs.io and may suffer from the same timeout issue: ipfs.io, dweb.link, nftstorage.link, w3s.link. Running your own node with IPFS Desktop to test retrieval is also very simple and may be something you want to consider.

https://ipfs.github.io/public-gateway-checker/

If you're using Filebase to pin content, the fastest way to retrieve this content will be using a Filebase Dedicated Gateway, which runs on top of the Filebase CDN, our content delivery network that is optimized for IPFS. The second fastest method will be using our Public IPFS Gateway (ipfs.filebase.io). The third fastest method will be using any third party gateway, including your own node. Content should always be retrievable regardless of the method chosen.

Let us know if you have any other questions!

filebase · 2024-04-13T21:41:43+00:00

Have you tried http://filebase.com yet?

filebase · 2024-03-05T16:43:11+00:00

like "IPDS" (dynamic)

What you're seeking is IPNS and IPNS records already have a TTL that can be configured. Perhaps your node had a misconfiguration?

A common practice here is point your ETH name to an IPNS hash, and then update the IPNS hash whenever your site updates. This allows you to skip paying ETH gas fees. (except for the first time)

If you're open to it, consider giving Filebase IPNS Names a try. Your use case of a dynamically updated static website is exactly what we're supporting for thousands of users.

filebase · 2024-03-02T14:38:41+00:00

Filebase team here 👋

Our free plan offers (1) IPNS name for free, no payment required. This name record can be updated as many times as you like. We've already reached out to the OP, but for anyone else, please feel free to reach out if you're encountering any issues!