Introducing Filebase Object Storage with Free Egress
Today we're launching Filebase Object Storage: fast, S3-compatible object storage with free egress, a built-in CDN, and a flat price of $15/TB per month. It runs on bare metal infrastructure that we operate and it's available now.
This is a return to where Filebase started — and the product we've wanted to use for years.
Why we built it
When we started Filebase in 2019, the pitch was straightforward: developers deserved better storage infrastructure. The hyperscalers were fast but expensive. The cheaper providers had rough edges. And nearly everyone treated egress as a way to lock you in.
Over the past few years, we spent a lot of time building IPFS and decentralized storage infrastructure. We're proud of that work — we ran some of the fastest IPFS gateways on the market and helped real teams put decentralized storage into production. But the market has settled, and the answer most developers arrived at is the one that's quietly powered the internet for years: S3-compatible object storage. It's where the tools live, where the workflows live, and where backups, AI datasets, media libraries, and application data actually sit in production.
So we came back to object storage — this time with the lessons of the last six years baked in.
Built from our own frustration
Filebase is a heavy user of object storage. We run offsite backups, archive infrastructure data, and move large files around constantly. Over the years we've used most of the major S3-compatible providers, and the same problems kept showing up: slow uploads, inconsistent download speeds, bandwidth bills that grew without warning, and API quirks that made automation harder than it should be.
One specific case stuck with us. While using Backblaze B2's S3-compatible API, we hit a response where ListObjectsV2 returned IsTruncated: true with no keys in the payload. If your backup tooling assumes well-behaved S3 semantics — and almost all of it does — that kind of edge case turns into a 3 a.m. problem.
After enough of those, we stopped working around other people's storage and built our own.
What you get
Filebase Object Storage is S3-compatible from the bucket level down. If your code already speaks S3, it already speaks Filebase. Point the AWS SDKs, rclone, restic, Terraform, or any other S3 tool at our endpoint and you're up in minutes. No gateway sitting in front of it, no protocol shim, no rewrite.
A few things make it different from what's out there:
Free egress. Storage costs what storage costs. Reading your data back doesn't cost extra. That single change makes backups, media delivery, and AI pipelines dramatically easier to model.
A native CDN. Most object storage stops at the bucket — if you want global delivery, you bolt on a separate CDN, manage another vendor, and hope cache invalidation works across both. We built the CDN into the platform. It's operated by us, sitting in front of the same buckets you upload to. Upload an object, serve it from the CDN.
Bare metal infrastructure we operate. We're not reselling AWS, GCP, R2, or B2. The hardware, network, storage engine, API layer, and CDN are all ours. That control is what lets us deliver the performance below at the price below — and fix things ourselves when they break instead of opening a ticket.
Content verification, built in. Every object can be deterministically hashed at ingest, giving you a verifiable fingerprint independent of where it lives. Useful for confirming backups, tracing AI training assets, and any workflow where provenance matters.
Performance
We benchmarked Filebase against Cloudflare R2, Backblaze B2, and Tigris using the same S3-compatible workload.
Writes (PUT):
| Provider | Throughput | Objects/sec | TTFB |
|---|---|---|---|
| Filebase | 258.60 MiB/s | 1,034 | 19 ms |
| Backblaze B2 | 67.99 MiB/s | 272 | 140 ms |
| Tigris | 54.79 MiB/s | 219 | 96 ms |
| Cloudflare R2 | 13.78 MiB/s | 55 | 365 ms |
Reads (GET):
| Provider | Throughput | Objects/sec | TTFB |
|---|---|---|---|
| Filebase | 352.09 MiB/s | 1,408 | 13 ms |
| Backblaze B2 | 143.39 MiB/s | 574 | 38 ms |
| Tigris | 118.62 MiB/s | 474 | 42 ms |
| Cloudflare R2 | 62.23 MiB/s | 249 | 82 ms |
In this run, Filebase wrote 3.8x faster than B2, 4.7x faster than Tigris, and 18.8x faster than R2. Reads came in at 2.5x, 3.0x, and 5.7x respectively. All tests were run from an independent server provider in the New York City area. Benchmarks don't capture every workload, but these numbers reflect what controlling the full stack actually buys you.
Pricing
Simple, transparent, and the same number you see on the marketing page.
Free — $0/month. 5 GB storage, 100K Class A requests, 1M Class B requests, free egress. Good for testing and small projects.
Pro — $7.50/month. 500 GB storage included, 1M Class A and 10M Class B requests, native CDN, and free egress. Additional storage runs $0.015/GB per month ($15/TB). Overages are $4.50 per million Class A and $0.36 per million Class B.
Enterprise — Volume pricing, migration help, SLAs, dedicated support, reseller arrangements, and higher limits. Get in touch.
No bandwidth fees. No retrieval penalties. No surprises at the end of the month.
What's next
This launch is the foundation, not the ceiling. On the near-term roadmap: account-level deduplication, team access with roles and permissions, expanded operational controls, better migration tooling, deeper usage visibility, and continued performance work.
Our goal is the same as it was in 2019 — make Filebase the fastest and most predictable place to store, move, and deliver data using the S3-compatible standard developers already know.
Try it today
Filebase Object Storage is live. Sign up at filebase.com, create a bucket, and point your existing tools at our endpoint. You'll feel the difference within the first few bytes.