Object Storage
A bucket for your files, served from the edge.
R2-backed object storage your agent provisions per tenant. Uploads and deletes go through an authenticated Worker; public reads skip it entirely and serve straight from storage.cohesivity.ai, while private reads stay on the authenticated path. Built for user assets, uploads, and static media.
durable by default
Keyed objects, kept safe
Every file lands in your tenant's own R2 bucket, addressed by a key you choose and stored with Cloudflare-grade durability. No volumes to size, no replicas to babysit — just put an object and it's there.
- uploads, avatars, and exports
- static media, served from R2
the read / write split
Guarded writes, open reads
Mutations run through a Worker that checks your application key first, so writes and deletes are always authorized. Public reads take a different route entirely — the object URL serves from storage.cohesivity.ai with no Worker hop — while private reads stay behind the authenticated path.
- writes & deletes — Worker-authenticated
- public reads — storage.cohesivity.ai, no key
pricing
Fluid pricing
Object Storage draws from your plan's monthly bucket; past that, usage auto-buys from fluid credit. Two things move the needle:
live storage
10 gb / month on free
uploads
10k / month on free
Object Storage gives every tenant an R2-backed bucket for the files an app actually ships — uploads, exports, user avatars, document attachments, and the static media your front end serves. Objects are addressed by key, stored durably on Cloudflare's network, and provisioned the moment your agent asks for them.
Related
R2, Buckets, Keys, Per-tenant, Durable storage
For more information, ask your agent.