A few decisions made before you order save you from rebuilding the server later. This checklist walks through them in order: what you will run, which operating system, how big, where, and how you will connect and look after it. Work through it once and your first order will match your workload.
Before you start
Have these to hand:
- A short description of what the server is for.
- The names of the main programs you will run, and their system requirements.
- Rough numbers: visitors, players, terminals, users or bots.
- Where your users, broker or team are located.
1. Define the use case
Write one sentence: "This server will run ___ for ___." For example, "three WordPress sites for my clients" or "two MetaTrader terminals for my own accounts". If you are still exploring, see what you can do with a VPS.
Note whether the work is:
- Always busy (a game server, scrapers) or mostly idle (a small site, a bot).
- For other people (hosting) or for you (a remote desktop).
2. Choose the product and operating system
- Linux VPS: websites, apps, Docker, databases, bots, most game servers. Managed over SSH.
- Windows VPS: Windows Server software, IIS,.NET, SQL Server, Windows-only services. Managed over Remote Desktop.
- Windows Admin RDP: a Windows desktop for remote work, trading terminals or desktop programs.
Check the software list from your preparation: if anything needs Windows, the choice is made. See Linux VPS vs Windows VPS.
Then pick the version:
- Linux: an LTS release your software supports, such as Ubuntu 24.04 LTS, Debian 12, AlmaLinux 9 or Rocky Linux 9.
- Windows: the newest version your software supports.
3. Size the plan
Size in this order:
- RAM: add up the OS and every program running at the same time, then add 25–50% headroom. See how much RAM a VPS needs.
- CPU: more vCPUs for many simultaneous visitors, terminals or players; faster cores for single-threaded workloads.
- Storage: OS, apps, data, logs and local backups, keeping 20–25% free.
- Network: check port speed and monthly transfer if you serve large files or heavy traffic.
If you are between two sizes, the larger one is usually the safer start for Windows and for shops. For a small Linux site or bot, start small and upgrade when the numbers say so.
4. Pick the location
Choose the location nearest to:
- your visitors for websites,
- your broker's server for trading,
- you for a remote desktop,
- your players for games.
5. Plan access and security
- Linux: decide whether you will use SSH keys from day one. Keys are safer than passwords.
- Windows: servers accept Remote Desktop on port 3389. Make sure your network allows outbound connections on that port.
- Plan to change the initial password and apply updates in the first hour.
- Note who else needs access and how you will give it to them.
6. Plan backups and extras
- Backups: decide where off-server copies will live. Do not assume backups are included in a plan.
- Register one elsewhere if you need it and point it at the server.
- Many people use a separate email provider.
- Control panel: if you want cPanel, Plesk or DirectAdmin, buy a licence from the vendor or use a free edition.
7. Review terms and billing
Read the terms of service and refund policy before you order, so you know how billing, renewals and cancellations work.
Check it works
Before you click checkout, confirm you can answer each line:
- Use case: written down.
- Product and OS version: chosen and supported by your software.
- RAM, CPU and storage: estimated with headroom.
- Location: chosen and, if possible, tested with ping.
- Access method and first security steps: planned.
- Backup destination: decided.
Troubleshooting
- Still unsure between two plans: ask MdmHost AI at /ai with your use case and numbers.
- Software requirements are unclear: ask the vendor before ordering, especially for panels and trading tools.