From request to access: availability, delivery times and payment

This article is for a manager or administrator ordering a dedicated server from us for the first time. It explains what the availability and delivery labels in the catalogue mean, what to write in the request, and what happens between the request and your first login.

What you will need#

• A clear idea of what you need: the line, the configuration and the country. If you have not decided yet, start with the articles on choosing a line and configuration and choosing a country.
• A decision on who pays: a company, a sole proprietor or an individual. For a company or sole proprietor, have the name and the company or tax number to hand.
• The name of a contact person and an email address that somebody actually reads. Phone and Telegram are optional.
• A few sentences for the comment: operating system, number of servers, timing, whether you need a private network; for Linux, a public SSH key too.

What the catalogue shows and why a configuration can disappear#

Every server in the catalogue is in stock. The catalogue shows availability separately for each country: Poland, Germany, France and the United Kingdom. A country’s tab shows how many server models are in stock there right now. Each country has its own set of configurations.

Availability is refreshed every five minutes. So the catalogue is a snapshot of the current state, not a fixed price list: a configuration you saw in the morning may be gone by the afternoon and come back later. In practice you may see this:

• the model is not available in the country you chose — the server page says so and shows the configurations in a country where it is;
• the model is not available in any country — its page is marked “Out of stock right now”; look at other servers or check back later;
• instead of tables there is a message, “The catalogue is being updated” — check back in a few minutes.

Within 12 or within 72 hours: what the delivery time means#

The “Delivery” column carries one of two labels next to each configuration. Both mean the server is in stock; the only difference is how long it takes to prepare that particular configuration.

• The clock starts at payment, not at the request. If time matters, do not put off paying the invoice.
• The time depends on the configuration and the country. For one model, some configurations may be labelled “within 12 hours” and others “within 72 hours”.
• The “within 12 hours — from …” note. In the catalogue, a model’s row shows the price and delivery time of its cheapest configuration. If a “within 12 hours — from …” note appears under a “within 72 hours” label, the model has another, more expensive configuration with faster delivery.
• The “Delivery within 12 hours only” filter leaves only the options with fast delivery in the catalogue.

Warning. “Within 12 hours” and “within 72 hours” are upper limits, not exact times. Do not schedule the switchover of a production system for the hour the term runs out: once delivered, the server still has to be set up and the data moved onto it.

Steps: from the catalogue to access#

1. Choose a country and apply the filters. In the catalogue, open the country tab; if needed, set the “Line” and “Processor” filters, tick “Delivery within 12 hours only” and press “Show”.
2. Open the server page and choose a configuration. The table gives the memory, drives, delivery time and price per month for each configuration; for some configurations a one-off setup fee is shown under the price. Select the row you need.
3. Fill in the “Request this server” form below the table. The fields are described further down.
4. Download a commercial proposal if you need one — the “Commercial proposal” button is next to the send button. It is handy when the spending has to be approved.
5. Press “Send request”. A “Request received” page opens with the request number, server, configuration, country, price and delivery time. Keep the number.
6. Wait for our reply. We will get in touch within one business day, confirm the configuration and issue an invoice in hryvnia.
7. Pay the invoice. The delivery time is counted from payment.
8. Receive your login details. We send them to the contacts in your request.

Form fields#

Which systems we can install#

We install the operating system before delivery, so state it in the comment to your request. You can choose:

• Debian 13 or 12;
• Ubuntu Server 26.04, 24.04 or 22.04 LTS;
• AlmaLinux or Rocky Linux 8–10;
• Windows Server 2016–2025, Standard or Datacenter, including Server Core — check the terms when we confirm your request;
• Proxmox VE 9, Proxmox Backup Server 4 or Hyper-V Server;
• cPanel or Plesk.

Your own image can be installed too — ask support how to provide it.

What to write in the comment#

The comment is optional, but it is what shortens the back-and-forth. State:

• The operating system from the list above, with the version, for example Debian 13.
• Your public SSH key — for Linux: we add it to the user on the server straight away. Send only the public part, the .pub file; never share the private key.
• The number of servers. The form takes only one configuration. If you need several identical servers, or other models as well, say so here.
• Timing — the date by which the server must be running, and whether that date can move.
• A private network — whether the servers need to be joined, within one country or between countries. Check on the server card whether the model you chose has one: the Lite and Turbo lines do not.
• The task and extra needs — in one sentence: an accounting system for 20 users, remote desktops, a standby site; whether you need extra IP addresses or a reverse DNS record.

Example: “Two servers with Debian 13 and a private network between them. They must be running by 20 October. We are moving an accounting database for 15 users from the office server.”

Price, commercial proposal and payment#

• Catalogue prices are in hryvnia per month and include VAT. Payment is monthly, by invoice in hryvnia; see the Payment page for details.
• The first payment is a month of rental plus the one-off setup fee, if one is shown for the configuration you chose; after that, only the monthly fee.
• The price in the table is fixed when you send the request.
• You do not have to fill in your contacts to download a commercial proposal in PDF. The document lists the configuration, what is included in the price, the country, the delivery time and the amounts. The proposal is valid for 3 business days; availability is confirmed when you order.

After payment: access and working through support#

We send the login details to the contacts in your request once the server is delivered. On Linux this is a user with sudo rights named after the distribution (for example, debian, ubuntu or rocky) and a password; root login with a password is disabled. On Windows Server it is an administrator account and a password.

We do not have a customer account or a control panel yet, so everything usually done in a panel is requested through support:

• a power-cycle reboot;
• reinstalling the operating system;
• the remote console — on request, on servers that have one (the Lite line may not);
• a reverse DNS record and extra IP addresses;
• connection to the private network;
• replacement of a failed drive.

Technical support is available around the clock: phone +38 044 206 08 08, email info@united.net.ua. The office is open from 9:00 to 18:00. What to include in a request is on the Technical support page. The exact parameters — addresses, how to connect to the backup space and so on — also come from support.

Warning. Access details are the keys to your server. Do not forward them to group chats, and straight after the first login carry out the steps from the first-hour articles.

What to prepare while you wait for the server#

• Linux. Create an SSH key on your own computer — the article on SSH keys explains how. If the public key was not in your request, send it to support before delivery. Also read the plan for the first hour on a Linux server.
• Windows Server. Read about the first hour on Windows Server and about secure RDP.
• Access. List the people who need to log in to the server, and find out your office’s external IP address and whether it is static: with a static address you can restrict access to SSH or RDP.
• Backups. Decide what to copy, where to and how often — the 3-2-1 rule will help. Backups do not switch themselves on: you set them up.
• Migration. If you are moving from another site, work through the migration checklist; for an accounting system there is an article on moving an accounting database.

How to check the result#

1. After the request. On the “Request received” page, check the server, configuration, country, price and delivery time.
2. On the invoice. The price of the server in hryvnia should match the price from the request; a setup fee, if one is shown for the configuration, is part of the first payment.
3. After delivery. Log in and compare the processor, memory and drives with the configuration you ordered; for the state of the drives and the array, see the article on checking RAID and drives. If something does not match, contact support straight away and quote the request number.

Common mistakes#

• Counting the time from the request. The “within 12 hours” clock starts after payment; before that come our reply within one business day and the invoice.
• Sending the form from a page opened hours ago. In that time the configuration may have run out and the price may have changed. Reload the page before sending. If the form asks you to choose again or says “The form has expired”, check your details and send it again.
• Mistyping the email address. It is the only required way to reach you; add a phone number or Telegram as a fallback.
• Taking Lite for a production system. It is a budget line for testing and non-critical workloads — with no private network or backup space, and it may have no remote console. For production systems we recommend Standard or Business.

What next#

• Dedicated server catalogue — availability and prices right now.
• Locations — countries and response time from Ukraine.
• First login: to a Linux server over SSH or to Windows Server over RDP.
• Basic Linux server hardening and the 3-2-1 rule for backups.