Flexible resources.
Your own virtual server.
Independent virtual servers built on our physical infrastructure using KVM virtualization.
Physical infrastructure meets virtualization flexibility
NEOIDC VPS uses KVM virtual machines on our physical servers, with Proxmox VE as the recommended platform. Customers manage their own OS, with backup and management offered separately.
Example VPS plans
Specifications are proposed examples, not confirmed offerings. Prices, public IP and traffic terms are determined through consultation.
VPS service policies
Local SSD / RAID per host
Each virtualization host uses local SSD and RAID. RAID does not replace backups.
Customer self-management
Customers manage their OS and applications. Access and responsibilities are defined by contract.
Optional paid backup
Backup frequency, retention and recovery support are selected separately. Recovery may be limited without backup.
Optional managed service
OS patches, checks and incident response are available under separate support contracts.
Availability and recovery
The basic local-storage service does not guarantee automatic failover or zero downtime. Recovery processes and targets are contract-specific.
From physical hosts to independent virtual machines
NEOIDC VPS runs Proxmox VE and KVM on our own physical servers. Each customer receives an independent OS with allocated vCPU, memory and disk resources, backed by local SSD/RAID on each host.
VM 01 · VM 02 · VM 03
Local SSD / RAID
VM 04 · VM 05 · VM 06
Local SSD / RAID
01 · Network & Access
Separate management and service traffic and apply firewall, VLAN and ACL policies as required.
02 · Virtualization Hosts
Create KVM virtual machines on Proxmox VE and assign vCPU, RAM and SSD by plan.
03 · Local Storage
Store VM disks on host-local SSD/RAID. Disk redundancy and data backup are separate controls.
04 · Backup & Recovery
Only subscribed VMs receive paid backups with agreed retention, schedules and restore testing.
Each host uses local, not shared, storage. RAID is not a backup. Automatic failover or zero-downtime recovery between hosts is not included in the basic service; recovery procedures and targets depend on the agreement.
Which is right for your workload?
Both provide independent operating systems, but differ in physical resource exclusivity and provisioning.
| Server Services | Dedicated Physical Server | VPS Virtual Server |
|---|---|---|
| Resources | Exclusive use of a full physical server | Allocated vCPU, RAM and SSD on a shared host |
| Scaling | Hardware upgrades or replacement by agreement | Plan adjustments subject to available host capacity |
| Typical use | Hardware-specific workloads and dedicated physical resources | Business websites, development and small-to-medium applications |
| Management | Self-managed or optional managed services | Self-managed with optional backup and managed services |
VPS for Different Business Workloads
Choose virtual server resources based on the scale and purpose of your workload.
Business Websites & Web Apps
Independent environments for business websites, web servers and applications.
Internal Systems & APIs
Dedicated OS environments for internal tools, business applications and API services.
Development & Testing
Separate environments for development, staging, functional testing and validation.
Frequently asked questions
Does each VPS have its own OS?
Yes. Each KVM VM has an independent OS environment managed by the customer.
Is backup included?
No. Backup is an optional paid service.
Is automatic failover included?
No automatic failover or zero-downtime guarantee is included in the base plan.
Can I resize resources?
Changes depend on host capacity and technical conditions.
Find the right VPS configuration
Share your use case, expected traffic and operating requirements for a tailored consultation.