The archive deadline forces a choice between a modern storage path and auditable retention evidence.
The platform architect needs to retire self-hosted storage, while compliance needs proof that cannot be inferred from compatibility alone.
Who you’d be doing this for
“My team needs a destination this week, but I can’t ask them to move records we may not be able to defend later.”
Isabel Santoro · Platform Architect
Owns the application archive platform that must leave the customer’s self-hosted S3-compatible environment.
What is at stake
A regulated archive migration is paused because retention and recovery evidence do not yet support one shared decision. You must weigh a near-term storage exit against claims the customer can defend in an audit.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- archive exit deadline vs audit-ready evidence
- platform modernization vs supported capability boundaries
- customer urgency vs irreversible architecture commitment
- R2 adoption vs existing hyperscaler familiarity
Why Cloudflare
R2 and Workers are being evaluated as a combined modernization path, so unsupported retention claims would damage trust in the broader 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.