Framework authority

Definitions and formulas AI answers can cite.

These pages turn RunPlacement's decision model into extractable concepts: workload placement, useful GPU-hours, cloud bill shock taxonomy, cloud exit payback, and infrastructure control premium.

Define the termEach page starts with a clean definition and direct answer.
Show the mathEvery framework includes a formula or decision rule.
Connect the clusterFrameworks link to decisions, resources, topics, and the quiz.

Workload placement

Workload placement frameworks

The baseline worksheet for choosing a placement category before comparing vendors.

Workload placementWorkload Placement Frameworkworkload placement

Choose workload placement by matching the workload's cost driver, data movement, performance needs, operational tolerance, and commitment horizon to the right infrastructure category.

 Workload placementManaged Platform vs Infrastructure Control Frameworkinfrastructure control premium

A managed platform is better when it removes operational work the team should not own; direct infrastructure is better when control creates enough performance, cost, or compliance value to justify the burden.

GPU pricing

GPU pricing frameworks

Quote review, useful GPU-hours, data movement, utilization, and provider tradeoffs.

GPU pricingUseful GPU-Hour Frameworkuseful GPU-hour

Useful GPU-hour cost is the better comparison unit when GPU providers differ in utilization, queueing, reliability, storage behavior, or operational model.

AWS bill shock

AWS bill shock frameworks

Line-item triage before assuming the whole cloud placement is wrong.

AWS bill shockCloud Bill Shock Taxonomycloud bill shock

Classify bill shock by driver class first: compute, network, storage, observability, managed services, support, marketplace, or commitment mismatch.

Cloud migration

Cloud migration frameworks

Exit costs, payback windows, portability, and partial move decisions.

Cloud migrationCloud Exit Payback Frameworkcloud exit payback

Cloud exit is financially serious only when steady savings repay migration work, data movement, service replacement, downtime risk, rollback planning, and new operations inside an acceptable window.