The media migration depends on preserving the work that begins after an upload.
The customer needs a simpler storage footprint while its engineers need a processing path they can observe and operate.
Who you’d be doing this for
“Uploads are the easy part, but I need to know where a failed transcode goes at 2 a.m.”
Henry Mueller · Staff Application Engineer
Owns the customer’s media pipeline and must approve a migration away from the self-hosted object store.
What is at stake
The customer can store media in R2, but cannot yet carry each upload into its processing flow. You must weigh a fast migration path against an operating model their engineers can trust.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- migration speed vs operational recovery
- existing client behavior vs reusable architecture
- event-driven processing vs smaller initial scope
- customer autonomy vs embedded support
Why Cloudflare
R2, Workers, and Queues place storage and application processing on the same developer platform.
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.