Backups, training sets, archives, app data, research, and logs. The same flat rate per TB, the same S3 API, and no egress fees whichever one you came for.
1 TB free for 30 days · No credit card required · No egress fees
Six patterns that share one trait: the data is large, it gets read back, and the reading is what makes it expensive somewhere else.
Write backups to a bucket with versioning and object lock, set when you create it. Under compliance retention, an object cannot be overwritten or deleted before its term is up, by anyone holding your keys. Restores carry no egress charge, so a recovery drill costs the same as not running one.
Keep datasets, checkpoints, and model artifacts in buckets your training code already knows how to read. Reading the same corpus for every epoch, or pulling it across to rented GPU capacity somewhere else, does not add a line to the bill. Large objects go up with multipart upload.
One storage class at one price. There is no cold tier, so nothing to rehydrate, no retrieval fee, and no minimum storage duration to plan around. Send a client a cut with a presigned link that expires on your schedule, up to seven days, instead of opening the bucket.
User uploads, exports, and everything else your product keeps. Point your SDK at a regional endpoint with path-style addressing and keep the code you have. Buckets stay private, and you hand out access with time-limited presigned URLs rather than public objects.
Choose Europe (France) or US East (Michigan) when you create a bucket, with more regions on the way. The region is fixed from that moment, and an access key works in one region only, so where a dataset lives is a property of the bucket rather than a policy someone has to remember.
Retention that does not get more expensive the longer you hold it. Logs and telemetry are billed per TB stored, with nothing charged per request on the way in or out. When the data has to survive for a fixed term, create the bucket with object lock and a retention period.
Storage is the only thing metered, at $4.99/TB/month. No request charges, no tier to choose, no minimum storage duration.
Data out to the internet, to another cloud, or back to your own servers is not billed, at any volume.
Keep your SDK or CLI. Point it at your region's endpoint, switch on path-style addressing, and carry on.
Governance or compliance retention plus version history, chosen when the bucket is created.
Give a key one bucket or all of them, read, write, list, or delete, and an expiry date if it should not outlive the task.
Europe (France) or US East (Michigan), decided per bucket and fixed from then on. More regions are on the way.
Pick the region, and turn on versioning and object lock if the workload needs them. Both are set at creation.
Grant one bucket or all of them, only the operations that service needs, with an expiry date if it should lapse.
Your region's S3 endpoint with path-style addressing. No SDK to swap and no rewrite.
rclone, the AWS CLI, or any S3 library. Multipart upload handles the large objects.
Fil One speaks the S3 API, so you keep the SDK and CLI you already use. Point it at your region’s endpoint, switch on path-style addressing, and authenticate with a Fil One access key. Everyday object work behaves the way your code expects: put, get, head, list, delete, presigned URLs, and multipart upload from your own SDK.
Buckets are private by default. For the operation-by-operation detail, including the calls that differ between regions, see the S3 compatibility reference in the docs.
Read Fil One docs, access the app to get started with no code required, or talk to someone on our team to get started.
After you create an account and provision your first bucket, migrating to Fil One is straightforward with our S3-compatible interface. Integrate directly into your codebase with any S3-compatible SDK, or migrate your data with a single AWS CLI command.
Enterprise teams who want more hands-on support can work directly with our team through every step of migration. Reach out at sales@fil.one to get started.
Egress is any data transferred out of your bucket: to the internet, to another cloud, or to your own servers. On a paid plan it is free at any scale, and there are no per-request charges either. The 30-day trial includes 2 TB of egress.
Billing is $4.99 per TB stored per month, with no fees for egress or API operations, subject to a $4.99 monthly minimum. Store under 1 TB and you pay the minimum; store more and you pay per TB for what you use.
Yes. Teams with predictable storage needs can talk to us about multi-year committed capacity. Contact sales and we will put a quote together.
You choose when you create the bucket: Europe (France) or US East (Michigan), with more regions on the way. A bucket's region is fixed at creation, so data written there stays there. Each region has its own endpoint, and an access key is scoped to a single region.
Running a GPU cloud? We can also install storage directly inside your own data center. See our partner program.
1 TB free for 30 days, with 2 TB of egress and no credit card. Move one bucket and compare the bill.
S3-compatible · $4.99/TB/month · Europe or US East