Server operations
Order a dedicated server
Choose hardware, location, operating system, billing term, and an optional SSH public key, then place an order against your account balance.
On this page
Before you start
- A signed-in Tungsto account with enough available USD ledger balance for the server order.
- A chosen configuration, US region, operating system, and weekly or monthly term.
- If you want key-based access, the contents of an SSH public key file. Keep the matching private key on your own device.
Prepare the deployment choices
Open the server catalogue first and compare CPU, memory, storage, network speed, and the stated provisioning window. The machine is dedicated to one customer, but a catalogue configuration is not proof that a particular physical unit is already assigned. Region capacity is checked again when the order is submitted.
Choose the operating system to record on the order. The list includes one-click images and a custom ISO option. Installation must be completed by the server operator before delivery. Windows Server and VMware ESXi availability does not include a licence; confirm that you can license the edition you intend to run.
- Choose the region for operational reasons such as latency, data location, and recovery planning—not from the headline capacity alone.
- Use the weekly term for short work and the monthly term for longer use; renewal follows the recorded term.
- Review quantity carefully because the server recalculates any volume discount and debits the full accepted total at submission.
Supply only a public SSH key
An OpenSSH key pair has two different files. A public key commonly ends in .pub and is intended to be copied to a server. The private key is the file without .pub; it proves your identity and must never be pasted into Tungsto, a support request, or the order form. The order endpoint accepts common OpenSSH public-key formats and stores the supplied public value with the order.
If you do not provide a public key, do not assume that a root password will appear later. The present account service neither collects nor returns a root password. Arrange the initial access method with the operator before relying on the deployment.
Submit and record the result
A successful response means the order was accepted, the ledger debit and server records were created together, and one provisioning action per server was queued. It does not mean the hardware is active. The dashboard may show a server in PROVISIONING, while the order form itself only retains the immediate success message.
The initial paid-through date is calculated when the order is accepted, using a seven-day weekly or thirty-day monthly term. Provisioning time is therefore inside that period. If delivery is delayed, retain the acceptance time and ask for the applicable resolution before relying on the machine.
- Open Account > Order server and select the configuration, region, operating system, term, and quantity.
- Optionally paste one complete SSH public key line into the SSH field.
- Review the estimated total. The browser estimate is informational; the service uses the catalogue to calculate the authoritative amount.
- Select Debit balance and place order once. Wait for the response instead of submitting several times.
- Copy the returned order reference and the success message into your change record.
Expected result and troubleshooting
If a server remains in PROVISIONING beyond the published configuration window, collect the order reference, server name, region, and submission time. Detailed delivery tracking is not yet available in the account. Contact the operator to confirm allocation, operating-system installation, and delivery.
| Result | Meaning | Next action |
|---|---|---|
| Order accepted | Balance and regional capacity passed validation; provisioning is queued. | Keep the order reference and wait for operator delivery. |
| Insufficient balance | The ledger sum cannot cover the authoritative total. | Add confirmed funds, then submit a new order. |
| Region unavailable or exhausted | The region has no configured capacity or its current count reached the limit. | Choose another region or contact the operator. |
| Order conflict | The same submission identifier is already being processed. | Do not create repeated charges; review the account and contact support with the reference. |