Match the workload
Allocate more CPU for compute-heavy work, more memory for active applications and more storage for growing data.
CUSTOM VDS BUILDER
Your resources.
Your resources.
Your configuration.
Choose processor, memory and storage independently. Your estimated monthly total updates as you build.
LIVE CONFIGURATION
—Processor
—Memory
—Storage
QUICK PROFILES
Start with a practical configuration.
Select a profile with one click, then adjust any resource below.
Review before ordering
The next screen summarizes the configuration and available service options before it reaches your cart.
Follow it in your panel
Orders, services, invoices and support requests stay connected to your customer account.
RESOURCE GUIDE
What should you allocate?
Think about what limits your application today and where its next stage of growth is likely to come from.
01
Processor cores
CPU capacity matters most for active calculations, parallel tasks, application workers and busier request processing.
- Application servers
- Build and automation tasks
- Concurrent workloads
02
Memory capacity
RAM keeps active applications and frequently used data available without relying on slower storage operations.
- Databases and caching
- Multiple running services
- Business applications
03
Storage space
Disk capacity should cover the operating system, applications, logs, user files and reasonable room for growth.
- Website and application files
- Database growth
- Logs and generated data
COMMON WORKLOADS
One VDS, many ways to use it.
Your ideal resource balance depends on how the server will be used.
Web applications
Host application runtimes, APIs, dashboards and content-driven projects with a resource profile matched to expected traffic.
Database services
Prioritize memory and storage headroom for structured data, indexes, cache layers and ongoing dataset growth.
Development environments
Create isolated environments for testing, staging, deployment tools and continuous integration workloads.
Business software
Run internal tools, management applications and remote services from a configuration sized for your team.
FROM BUILDER TO PANEL
A clear path to your server.
Every decision is reviewed before the configuration is added to your cart.
RESOURCE PROFILE
Choose CPU, RAM and disk
Start from a ready profile or select each resource separately.
SYSTEM OPTIONS
Select the operating system
Review available system templates and optional network choices.
ORDER REVIEW
Confirm the configuration
See the resource summary and calculated amount before checkout.
CUSTOMER PANEL
Follow everything together
Keep orders, services, invoices and support under one account.
A defined server environment for a growing workload.
A Virtual Dedicated Server uses virtualization to create an independent server environment with a defined processor, memory and storage allocation. It gives applications their own operating environment without requiring an entire physical machine.
The practical advantage is control over resource balance: CPU can be prioritized for processing, RAM for active datasets and storage for files, databases and logs.
Virtual isolation
Your server environment is separated at the virtualization layer, keeping its operating system and applications distinct from other virtual environments.
Purpose-built sizing
Instead of choosing only a generic label, you can shape the configuration around the workload that will actually run.
Server-level use cases
A VDS can support web stacks, APIs, databases, development tools, background workers and private business applications.
Capacity planning
A clear resource baseline makes it easier to monitor usage and decide which part of the server needs more headroom later.
BEFORE YOU CHOOSE
Six questions for better sizing.
A useful starting configuration accounts for normal usage, busy periods and the operational work around the application.
What will run?
List the application runtime, database, control panel, cache, queue and any monitoring tools that will share the server.
How busy can it get?
Consider simultaneous users, scheduled jobs, API requests and traffic peaks rather than planning only for the daily average.
How fast will data grow?
Include databases, uploads, logs, temporary files and generated content when estimating long-term storage demand.
What does the software need?
Check minimum and recommended requirements for the operating system, application stack and every supporting service.
Where is headroom needed?
Leave capacity for deployments, maintenance, short traffic spikes and background tasks so normal operation is not at the limit.
What is the recovery plan?
Plan how application data will be backed up, tested and restored; server capacity and a backup strategy solve different problems.
WHERE VDS FITS
Choose the right hosting layer.
Each model serves a different stage. The right choice depends on required control, isolation and resource flexibility.
ENTRY LEVEL
Shared hosting
A managed, shared environment for straightforward websites with limited server-level requirements.
- ControlPlatform-defined
- ResourcesShared plan limits
- Best fitSimple sites
FLEXIBLE MIDDLE
Virtual dedicated server
An independent virtual environment with a configuration that can be balanced around the application.
- ControlServer environment
- ResourcesDefined configuration
- Best fitGrowing workloads
PHYSICAL SCOPE
Dedicated server
A complete physical machine for workloads that specifically require full hardware-level scope.
- ControlFull machine
- ResourcesPhysical hardware
- Best fitLarge-scale needs
VDS GLOSSARY
Know what you are configuring.
Understanding the main server terms helps turn a list of numbers into a practical configuration.
vCPU / Core
Virtual processing capacity used by application workers, calculations, compression, builds and concurrent request handling.
RAM
Working memory for active services, database operations, caches and data that applications need to access quickly.
Disk capacity
Space for the operating system, application files, databases, uploads, packages, temporary data and logs.
Operating system image
The starting system template on which the application stack, services, security settings and management tools are installed.
Network usage
Traffic generated by visitors, APIs, downloads, updates, backups and communication between external services.
Operational security
The ongoing practice of applying updates, limiting access, monitoring services and keeping recoverable copies of important data.
VDS QUESTIONS
Plan before you build.
Useful answers for choosing a custom virtual server configuration.
How do the quick profiles work?
A quick profile selects a processor, memory and storage combination for you. Every selection remains editable in the resource builder below.
Should I prioritize CPU or RAM?
CPU is more important for computation and parallel processing. RAM becomes more important when applications keep larger working datasets active or several services run together.
How much storage headroom should I leave?
Include space for the operating system, applications, user data and logs, then leave additional room for expected growth rather than sizing only for today's usage.
When do I select the operating system?
After the resource selection, the next step shows the operating system templates available for the chosen disk capacity.
Can I review the price before checkout?
Yes. The estimated monthly amount updates in the builder, and the complete selection is shown again before it is added to the cart.
What if I am unsure about the starting size?
Begin with the software's documented requirements, add the resources used by supporting services, then leave reasonable headroom for peak activity and maintenance.
Why should I avoid running at the resource limit?
Deployments, scheduled jobs, traffic spikes and temporary processes can require capacity beyond the normal average. Headroom helps absorb these short increases.
Should production and testing share one server?
Separating production from development or testing reduces resource contention and lowers the chance that an experiment affects a live workload.
What should I check before moving an existing application?
Record current CPU, memory, storage and traffic usage; verify software compatibility; estimate data-transfer time; and prepare a tested rollback or recovery path.
Does more storage make the server faster?
Capacity and performance are different measurements. More space prevents capacity pressure, while application speed also depends on CPU, memory, software design and storage characteristics.
READY TO CONFIGURE?
Return to builderBuild around your workload, not a generic label.
Select a quick profile or fine-tune every resource yourself.