Start with your application's requirements
A VPS gives your software an operating system and a defined allocation of virtual CPU, RAM and disk space. The right size depends on the software, its configuration and the work it does. A visitor count alone cannot tell you how much RAM a database needs or how quickly an application will respond.
Memory: include the operating system
RAM must cover the operating system, background services and your application at the same time. Check the software's recommended memory rather than only its minimum installation requirement. A database, control panel and application running together need more room than one small service.
Fasting Host Nano has 1 GB RAM and offers Debian 12 or 13. Start has 2 GB RAM and a broader Linux/FreeBSD list. Basic starts at 4 GB RAM and adds Windows choices. The range continues to 32 GB RAM. These are resource allocations, not promises about how many websites or users a plan can support.
CPU: consider the type of work
Fasting Host plans range from 1 to 8 vCPU. An application handling occasional requests has different CPU needs from a build job or busy database. Review the software's thread support and measure CPU use under a representative workload. More vCPU cannot fix an application blocked on slow external requests or an inefficient database query.
Storage: leave room to operate
The SSD allocations range from 15 GB to 200 GB. Allow for the OS, updates, application files, database growth and logs. Keep independent backups outside the VPS; a copy stored only on the same server does not protect you from losing access to that server. Decide how you will restore data before the application becomes important.
Compare exact CPU, RAM, SSD and monthly prices for all eight plans.
Choose an OS your software supports
Use your application's supported-platform documentation as the starting point. Confirm the required version, available security updates and management tools. Familiarity matters too: choose a system you can maintain, or arrange help before deploying it.
- Nano: two Debian choices, Debian 12 and Debian 13.
- Start: 18 Linux and FreeBSD choices.
- Basic through Elite: 24 choices covering Linux, FreeBSD and six Windows options.
Not every application works on every family, and not every plan exposes every template. The checkout selector shows the current versions available for the chosen plan. Seeing a template in that list does not remove the need to check its update/support lifecycle and your software's requirements.
Linux and FreeBSD administration commonly uses SSH; Windows administration commonly uses Remote Desktop. Restrict administrative access, maintain a recovery path and avoid exposing unnecessary services to the public internet.
Understand location and shared networking
Fasting Host VPS infrastructure is in the Netherlands. That can suit projects serving a European audience, while users in other regions will have different network routes and latency. A worldwide audience does not mean a server is physically close to every visitor. Test your application from the locations that matter to your users.
The plans share a 10 Gbps host uplink. This describes the host's uplink, rather than a dedicated 10 Gbps connection or guaranteed application throughput for each VPS. Traffic is unmetered subject to the Fair Use Policy. Review the policy against sustained transfers, backups and other bandwidth-heavy work before ordering.
Check current address availability and any workload-specific network needs in checkout or with Fasting Host support. Do not assume a location or protection feature that is not stated for your configuration.
We serve customers worldwide. Current SSD Cloud VPS plans run at Digital Realty AMS5 in the Netherlands. NVMe M.2 servers at SkyLink Data Center B.V. in Eygelshoven are planned next, followed by additional locations. Upcoming hardware and locations are not available to order yet.
Plan how the server will be maintained
Root or Administrator access lets you install and configure your software. It also means planning operating-system updates, application updates, firewall rules, access control, monitoring and backups. Keep private SSH keys private, use strong unique credentials and store recovery information securely.
Monitor memory, disk capacity and CPU after launch. Use measurements from your actual workload to decide whether resources are sufficient. Establish backup frequency and retention based on how much data you can afford to recreate, and test a restoration rather than relying on a successful backup message alone.
Read the backup and security policy and service availability and support policy. Ask about your specific management needs before assuming they are included in the monthly plan.
A short checklist before checkout
- Write down your application's supported OS and recommended CPU, RAM and disk requirements.
- Choose a plan with room for the OS, updates, logs and expected growth.
- Check the exact OS version in that plan's live selector.
- Review the USD monthly price, shared-uplink conditions and relevant policies.
- Prepare secure server access and an independent backup/recovery plan.
- Review the configuration and account information before paying.
After payment confirmation, automatic provisioning starts. Manage the resulting service in your client area. No fixed activation time is promised here; configuration, inventory and operational conditions can affect it.
Compare monthly and annual totals: annual Cloud VPS billing provides twelve months at ten monthly payments. Every newly purchased service has a seven-day refund guarantee from initial activation. Read billing and refund details.