Summary
Decide which remaining hosted/cloud responsibilities should move into the self-hosted Docker stack to reduce cost, improve reviewer latency, or simplify maintenance.
Context
Some hosted resources may still provide useful behavior, while others may be leftovers from the old cloud version. Moving everything blindly into Docker can increase stack complexity, so this should be a tradeoff review rather than a default migration.
Requirements
- Start from the Cloudflare inventory and current self-host architecture.
- Evaluate cost, latency, reliability, maintenance burden, and data ownership for each candidate.
- Identify which features belong in the core stack, optional compose profiles, or hosted-only integrations.
- Keep beginner-friendly Unraid defaults in mind.
- Preserve escape hatches for advanced operators where reasonable.
Deliverables
- Decision matrix for each candidate hosted feature.
- Recommended migration order with risk and rollback notes.
- Any needed compose, docs, config, or migration follow-up issues.
- Explicit non-migration rationale for anything that should stay hosted.
Acceptance criteria
- No hosted dependency is removed without a replacement or a documented decision to keep it.
- Recommendations include operational tradeoffs, not just cost savings.
- The output is concrete enough to drive implementation issues.
Summary
Decide which remaining hosted/cloud responsibilities should move into the self-hosted Docker stack to reduce cost, improve reviewer latency, or simplify maintenance.
Context
Some hosted resources may still provide useful behavior, while others may be leftovers from the old cloud version. Moving everything blindly into Docker can increase stack complexity, so this should be a tradeoff review rather than a default migration.
Requirements
Deliverables
Acceptance criteria