Integrity evidence must be available without slowing the object path developers already trust.
Pilot users need proof that retrieved data matches their upload, while the gateway must preserve compatible, low-latency requests.
Who you’d be doing this for
“Our security review asked for proof on restores, and I only have a script nobody wants to own.”
Hirut Mutua · Platform Engineer
Maintains backup and media pipelines for an application development organization evaluating R2.
What is at stake
Developers lack a supported way to verify that retrieved R2 objects match what they uploaded. You must weigh integrity evidence for pilot workloads against compatibility and latency on every request.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- integrity evidence vs request-path latency
- S3 compatibility vs new developer controls
- durable metadata vs storage-path coupling
- broad application coverage vs focused pilot scope
Why Cloudflare
R2 sits on the request path for application data that developers need to retrieve reliably across the global network.
Written with these in mind
Not your kind of problem? 51 more at Cloudflare, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.