Configure a first Linux VPS order
Prepare a Linux VPS order by checking workload capacity, compatible region and image, full billing total and the checkout boundary.
Content revised · English
- Guide type
- Account & orders
- Examples
- Illustrative, environment-specific
- Integration scope
- No remote machine connected
Write down the application requirements
Estimate the memory working set, disk usage with growth and recovery copies, CPU load and monthly transfer. A port speed does not describe the amount of data included. Select a Linux VPS when you need your own system and root access; use another product family for Windows, GPU or managed web requirements.
Example: compare Umbra 1 and Umbra 2
Umbra 1 lists 1 vCPU, 2 GB RAM, 25 GB NVMe and 1 TB monthly transfer. Umbra 2 lists 2 vCPU, 4 GB RAM, 60 GB NVMe and 3 TB monthly transfer. This is a capacity comparison, not a performance benchmark. Measure the complete application, including the database, operating system, logs and update headroom, before deciding that either plan fits.
Choose a compatible plan, region and image
Open the catalogue, compare the exact capacity and enter Configure. The region and system-image choices are limited by the selected plan. An operating system that appears on a different product is not automatically supported here. A geographic location should suit both the audience and the project’s data handling.
Compare the full payable period
The checkout offers monthly, annual and biennial periods. Read the full total and its term; a displayed monthly equivalent for a longer term is not a promise of monthly payments. Review the proposed refund policy because the product and elapsed time change eligibility.
Check the payment network and summary
Review the plan, image, location, term and total together before selecting a prepared crypto method. BTC, LTC, ETH, TRX, SOL and the listed USDT/USDC networks are distinct routes. A token symbol alone is not enough to choose the transfer network. There are eight checkout routes across seven assets; XMR is not accepted.
Inspect the order
Continue to checkout and the private workspace. The order stores its configuration and can receive an expiring server quote with a configured fixed address. Blockchain monitoring and actual provisioning are not connected. No real server IP, SSH password or console is created; a future live service would begin its provisioning clock only after verified payment.
Leave with a verifiable result.
- Record application version, memory footprint, disk growth, monthly transfer and recovery requirements.
- Confirm the exact plan's listed region and operating-system image.
- Review the full billing-cycle total and any add-on units.
- Save the order and verify the selected configuration.
- For a future live server, validate secure access, application behaviour and an independent restore.