Price lift-and-shift separately from workload redesign

When comparing container platforms with different billing semantics, publish two cost cases: unchanged workload shape and redesigned workload shape. A lift-and-shift estimate must preserve always-on workers, requested resource floors, network paths, and high-availability replicas. A redesign estimate may assume request concurrency, scale-to-zero, queue-triggered workers, or scheduled jobs, but must include the engineering work and latency trade-offs. Blending these cases creates a cheap number that the initial migration cannot achieve.

Applies when: moving from actual-use metering to allocated containers or request-based serverless. Keywords: Railway AWS ECS Cloud Run migration cost lift shift redesign