Stopping the application can leave other charges running
A stopped preview environment may still contain allocated resources. Before treating a pause as a cost saving, compare the provider's actual line items with the resources the organisation intends to keep.
This worked example uses a fictional hosting arrangement and explicitly invented rates. It is a planning comparison, not a Faith Forge Labs quote, a current provider price or a recommendation to delete an operational resource.
Read the inspected arrangement line by line
A service business has a private preview environment for reviewing a revised staff application. Its fictional provider arrangement has three separately metered resources:
| Resource | Assumed rate in this example | Effect of the supported Stop operation |
|---|---|---|
| Compute instance | R120 per day while running | Compute metering stops |
| Retained data volume | R8 per day while allocated | Volume remains allocated and metered |
| Reserved address | R2 per day while reserved | Address remains reserved and metered |
The table describes the inspected fictional arrangement only. A real provider may use different units, minimums, storage rules or address treatment. Its actual billing documentation and account configuration must establish the comparison.
The business plans a five-day pause while the authorised reviewers are unavailable. Someone estimates that stopping the instance will make the preview cost nothing for those days. That estimate considers only compute.
Under the stated rates, keeping everything running would cost R650 for five days: R600 compute, R40 volume and R10 address. Stopping compute while retaining the other two resources costs R50. The pause changes the amount; it does not eliminate every charge.
Compare the alternative that really removes the resources
The provider also supports releasing the volume and address. Those actions have different consequences from Stop. Releasing the volume requires a deliberate decision about the data it holds, and the team cannot assume that a later address allocation will reproduce the same endpoint.
The owner examines what would be needed to recreate a usable preview: an authorised export, the required configuration, a supported restore procedure, new resource allocation and a check of the complete staff task. The current handover does not yet include a rehearsed recreation of this environment.
A file labelled “backup” is not enough to mark that alternative ready. The reviewer needs evidence that the required records, configuration and permitted access can be restored in the arrangement being proposed. Those checks are separate from the provider's ability to release a billed resource.
Make a decision that includes readiness
For this short pause, the owner selects Stop with the volume and address retained. The decision accepts the stated R50 continuing charge for the five days and records the date on which the paused environment will be reviewed again.
The reason is concrete: there is no available review window to complete the recreation rehearsal before the team needs the preview back. The owner does not describe retained storage as free, and the plan does not claim that future recreation is already proven.
The chosen scope also avoids a misleading comparison between R50 and an assumed zero-cost recovery. The effort, availability and checks needed to recreate the preview have not yet been estimated or accepted. Unknown work should remain visible rather than being treated as zero.
For a longer pause, the organisation may choose a separate recovery rehearsal and resource-release decision. That is a future option with its own evidence, not an automatic extension of the short-pause plan.
Check the resource state against the decision
The fictional review record identifies the compute instance, volume and reserved address separately. It states the expected paused configuration: compute stopped, volume retained, address retained. It also identifies the account owner who may authorise any actual resource change.
A provider's later usage or billing record would be needed to verify real charges. A button labelled Stop and a cost estimate cannot establish that the intended account action occurred or that every billing period has closed. Keep estimated, observed and invoiced amounts distinct.
The production environment is outside this pause decision. Its resources are not released merely because their names resemble the preview resources. An unrelated document store is also excluded from the selected set. The resource list is part of the scope, not an optional administrative detail.
Keep the decision usable at the next review
Record what remains allocated, why it remains necessary, who owns the account and when the decision will be revisited. Include the expected consequences of releasing each resource rather than using “cancel the environment” as an ambiguous instruction.
This is particularly useful when a project pauses for language or business review. Development activity may stop while subscriptions and allocated infrastructure continue. The project plan should make those dependencies understandable to the people approving expenditure.
The pricing and scope page separates development deliverables from operating commitments. Bring the actual provider arrangement and resource inventory to a project discussion if a paused application has costs the team cannot explain.