Identify the exact offer
Save the official programme page and the date you read it. Establish whether you are using a time-limited trial, a recurring allowance or promotional credit. A marketing headline rarely explains every resource, region and account condition that determines eligibility.
Read the transition rules before adding a payment method. Check whether an upgrade requires an explicit action, whether resources stop at expiry and whether unused credits disappear. Do not infer those rules from another cloud provider; account behaviour varies.
Make a resource inventory
Write down everything the deployment creates, including the items created by a setup wizard. An application may use a VM, a boot disk, an extra volume, an address, a snapshot and an external service. Evaluate each item against the offer independently.
Scroll sideways to see the full table
| Resource | Question to answer |
|---|---|
| Virtual machine | Are this shape, region and usage eligible? |
| Storage | Which disk type and capacity are covered? |
| Backups | Are snapshots or backup storage included? |
| Networking | What are the traffic and address charges? |
| Optional services | Did the wizard add a billable component? |
If the final estimate is unclear, stop before provisioning and inspect the individual line items. Keep the inventory with your deployment notes so you can find resources again when removing the project.
Calculate the workload you will actually run
For an illustrative example, imagine a small test service with 20 GB of outbound traffic, a 25 GB system disk and a separate 10 GB backup. These are planning figures, not a provider quota. Check all three against the relevant allowance instead of counting only the VM.
Allow for repeated downloads, logs, updates and backup retention. A public endpoint can receive unexpected requests, so normal test traffic is not necessarily the upper bound. Decide whether you need application rate limits or a smaller exposed surface before publishing it.
Use alerts without treating them as a spending cap
Configure the available billing notifications and verify who receives them. Then read whether the service actually enforces a hard limit or merely sends a message. A notification cannot by itself stop a running workload or undo usage already incurred.
Where supported, use quotas and access controls to reduce accidental provisioning. Review usage after the first deployment and after significant changes. Check actual billing data, not just the estimate shown before creation; the two answer different questions.
Understand stopped versus removed
Stopping a VM may leave disks, addresses or other resources allocated. Read the deletion behaviour and decide which data must be exported first. A retained disk can be useful for recovery, but it must remain visible in your inventory and cost review.
Use the account resource list to find objects that outlive the machine. Check the applicable billing period after removal. Keep a record of what was removed and when, especially if several projects share the same account.
Plan the end of the trial
- Export application data and configuration before the expiry date.
- Test the exported copy in a different environment.
- Decide whether to upgrade, migrate or shut down the experiment.
- Remove resources you no longer need, including retained extras.
- Review usage and billing after the change.
An experiment is easier to leave when deployment is documented and backups use a portable format. Avoid making a proprietary optional service essential unless you have also checked its export and replacement path.
A clear pass or fail decision
The offer passes your review when the complete configuration is eligible, the limits fit your experiment and you understand the exit procedure. Missing capacity, unclear billing or a required paid component are reasons to reconsider the setup before committing data.
For an overview of the different free models, read free Ubuntu VPS options. For Linux practice without a cloud bill, use the local virtual machine walkthrough.
Questions and answers
Will a billing alert stop charges?
Only if the service explicitly documents an enforcement mechanism tied to it. Treat a notification as a warning until you have verified otherwise.
Can I delete the VM and keep my data?
Export and test a backup first. Disk retention and deletion rules differ, and a retained cloud disk may continue to incur charges.