Object Storage
Browse all articles, tutorials, and guides about Object Storage
Posts
Free Egress Has Fine Print: S3 vs R2, B2, Wasabi and More
Serving 50 TB a month costs $4,379 on S3 at list price and $62 on R2. But the cheapest number in our comparison is outside the free-egress policy of the provider that offers it. Nine storage offerings, four workloads, and the fine print that changes the answer, with a calculator you can run yourself.
Migrating From S3 to Branch-Aware Storage
Neon object storage is S3-compatible, so moving to it is mostly a config change, not a rewrite. Your upload code, your presigned URLs, and your download paths all stay the same. Here is exactly what carries over, the small diff that changes, and a copy script to move the objects, with the honest list of what does not come along.
Stop Standing Up an S3 Bucket Per Preview Environment
Giving every preview environment isolated file storage usually means provisioning a real bucket per environment: policies, IAM, lifecycle rules, credentials, and a teardown job that leaves orphans anyway. When the bucket rides the database branch, that whole apparatus disappears. Here is the difference, tested.
Presigned-URL Uploads From a Serverless Function
Streaming user uploads through your API means the bytes cross your server twice, and serverless functions have request-size limits that make it worse. Presigned URLs let the browser upload straight to object storage while your function just hands out permission. Here it is on a Neon Function, tested end to end.
Object Storage That Branches With Your Database
Database branching gives you a throwaway copy of your rows. But your app also stores files in object storage, and those normally stay in one shared bucket. On Neon a branch forks the bucket too, so each branch gets its own copy of the files. I built a small files API to prove it.