Here's how to leave.
Read it before you start.
S3-compatible, $0 egress. The exit is a documented one-line command, not a renegotiation. You can verify the way out before you ever commit.
No credit card required · No egress fees · Connects in minutes
Every vendor says "no lock-in." Few will show you the exit.
If you've been burned before, the claim isn't enough — you want to see the way out before you put data in. With most providers, you only discover the real exit cost when you try to leave.
Leaving 100 TB costs $9,216 on AWS.
At $0.09/GB internet egress, the bill to move data out scales with how valuable your dataset has become. The lock isn't in the contract — it's in the exit invoice.
A non-S3 API means leaving is a rewrite.
When the storage API is bespoke, exiting means re-engineering every integration. The switching cost is engineering time, and it grows with every feature you build on top.
You learn the cost only when you try to go.
Most teams never run the migration until they have to — by then the dataset is large, the egress bill is real, and the 'no lock-in' promise meets the actual number.
The way out is one command and $0.
Here is the migration off Fil One — before you've put anything in. Same S3 API on both ends, no egress charge to move data out.
Public US rate cards, Q2 2026. AWS: 102,400 GB × $0.09 = $9,216. GCP tiered (10 TB @ $0.12 + 40 @ $0.11 + 50 @ $0.08) = $9,831. Azure tiered = $7,602. Fil One: $0 egress.
Portable by default, provable on day one.
Full S3 parity
Standard S3 API. The tools that read and write Fil One are the same ones that read and write everywhere else — so the migrate-off command is one you already know.
$0 egress on exit
Moving your data out costs nothing. The exit isn't a renegotiation or a budget request — it's a sync command you can run today, for free.
Flat, predictable cost
$4.99/TB/month while you stay. No egress, no per-request fees — the bill that would normally make leaving expensive doesn't exist.
Integrity-verified data
Every object is verified approximately every 24 hours, so the data you eventually move out is provably the data you put in.