Understand what the architecture will cost.

A server price is a starting point. Follow the capacity you keep, the demand you serve, the data you move and the work your team still owns.

Cost PlannerFive answers identify measurements and costs to include. This is a planning checklist, not a price quote.5 questionsLive prioritiesNext steps Start planningClose section

Prepare your cost checklist.

Five questions about one workload. Identify what to measure, what to include and which assumptions need evidence. No prices are calculated: rates, contracts and workload measurements belong in your estimate.

  1. Question 1 of 5 · Demand

    What does demand look like over a typical week?

    Choose the pattern for one workload. If you have no measurements, keep that uncertainty visible.

    Choose one No answer selected

  2. Question 2 of 5 · Baseline

    Can any capacity safely stop when there is no work?

    Consider restart time, scheduled jobs and availability requirements—not just office hours.

    Choose one No answer selected

  3. Question 3 of 5 · Data movement

    Which data routes must the estimate include?

    Include application traffic, replication, backups, logs, exports and recovery exercises.

    Choose one No answer selected

  4. Question 4 of 5 · Operating effort

    Who owns the work after deployment?

    Include patching, application incidents, access, support, backup checks and recovery tests.

    Choose one No answer selected

  5. Question 5 of 5 · Commitment

    How confident are you about future eligible usage?

    A discount commitment should follow the workload forecast. Do not infer a stable baseline from a monthly average.

    Choose one No answer selected
Four costs behind the server priceSee how releasing capacity, scaling and moving data affect the bill.CapacityDemandTransferOperations ExploreClose section

Four costs hiding behind the server price.

Make a harbour decision. Watch the cost change. Apply the question to your workload.

Figure 01 Idle capacity
Four chartered vessels: one working, three idle. Releasing two leaves one working vessel and one spare. CHARTERED CAPACITY · ILLUSTRATIVE Carrying cargo Spare capacity Idle charter RELEASED Idle charter RELEASED

Idle capacity can still be on the bill.

Like chartered vessels, allocated cloud capacity can cost money while idle. Release only what you can safely spare; stopping an app may leave its resources billable.

Ask about your workload

Which capacity can you safely release or schedule off, while keeping enough ready to meet your service target?

Figure 02 Scaling
Two baseline vessels remain ready. Two extra vessels travel into position to handle peak demand. BASELINE + PEAK CAPACITY Baseline Baseline Peak capacity Peak capacity

Price the peak, not just the average.

A busy harbour needs extra vessels. Cloud capacity has the same trade-off: more capacity serves the peak, and its duration determines the extra cost.

Ask about your workload

What baseline, peak duration and scaling delay must you plan for—and what happens at your capacity limit?

Figure 03 Data transfer
Cargo travels from the source port to the destination. Measure each direction separately before applying service-specific rates. N MEASURE VOLUME × CHECK THE ROUTE’S RATE SOURCE DESTINATION OUTBOUND · REGIONS / PROVIDERS / INTERNET Return traffic may have a different charge.

Every data route needs a price.

Shipping cargo adds a journey cost. For cloud data, check the route, direction and volume—plus any processing fees. Local traffic is not always free.

Ask about your workload

Which routes carry your data, in each direction, and what transfer, gateway and retrieval fees apply?

Figure 04 Operational effort
Dock maintenance moves from your team to the port operator. Cargo checks and delivery decisions stay with your team. HAND OVER A TASK · KEEP AN OWNER YOUR TEAM PORT OPERATOR Dock maintenance Cargo checks Delivery decisions

A smaller invoice can hide more work.

Handing dock maintenance to an operator raises its fee but frees your crew. Managed cloud services can do the same; your team still owns the application.

Ask about your workload

Who will own routine work, support and recovery—and what will their time cost alongside the provider invoice?

Billing and operating costsSelected articles and primary sources for the decisions that need a closer look.Practical articlesSource documents Browse notesClose section

Read the detail behind the decision.

These three existing articles have been fact-checked and revised: what budgets enforce, when commitments save, and what support leaves your team to do.