Entry resources
DC VDS 1
Check the combined requirements of your operating system and application before starting with the entry plan.
- CPU
- 1 Core
- Memory
- 2 GB DDR4
- Storage
- 40 GB NVMe SSD
Self-managed virtual server
View this planVDS Server Hosting
Configure the operating system and server software your application needs. Compare CPU, memory and NVMe storage on self-managed VDS plans using a shared hypervisor uplink.
“I have been using DCHost services for almost a year. They offer excellent quality and speed, all at a very reasonable price. Excellent support and uptime.”
“Professional service at a decent price. DCHost is really one of the best hostings I’ve ever worked with — professional team, professional support.”
“One of the best sites where I could buy a Turkish server is DCHost; they have very good support and they answer your questions and requests well.”
Istanbul location
Measure the latency between your connection and our Istanbul location. Start the test below to see your ping in milliseconds (ms).
Results depend on your internet provider, connection type and current network conditions.
A closer comparison
Use these examples to compare the resources assigned to each virtual server. Choose against measured application use and allow room for the operating system, database and background processes.
Entry resources
Check the combined requirements of your operating system and application before starting with the entry plan.
Self-managed virtual server
View this planMore resources
Compare the extra CPU and memory for an application running alongside a database or background jobs.
Self-managed virtual server
View this planLarger workloads
Compare a larger allocation when measured peak use calls for more memory, processing capacity or disk space.
Self-managed virtual server
View this planAll three options have the same self-managed model and use a shared hypervisor uplink. A larger plan changes resources, not who patches the operating system, monitors applications or prepares backups. If your team needs ongoing software administration, compare the scope of managed server services.
Explore managed server servicesApplication resource planning
A virtual server plan needs to accommodate the web process, database, cache and background tasks that make an application work. Visitor counts alone cannot describe that demand. Compare the listed VDS resources with measurements from a representative workload, then allow capacity for traffic peaks, software updates and the next stage of your project.
Estimate the cost of a request as well as request volume. Authentication, image processing and external integrations can create very different CPU and memory demand. Test a typical user journey, record response times and watch worker queues so that a slow dependency is not mistaken for a lack of server resources.
Reserve memory for the operating system, application workers and database together. Large queries, connection counts and caching rules affect the amount required. Follow disk growth for uploads, database files and logs; a plan with sufficient memory can still run out of storage during an import or backup operation.
ERP integrations, reporting tools and job queues often have busy periods outside normal browsing hours. Include scheduled exports and simultaneous tasks in your test. Check operating system compatibility and any software licence conditions before selecting the environment, particularly when moving an existing application from another provider.
Selection guide
DCHost's VPS and VDS pages currently use the same product catalogue. This guide focuses on application sizing; the names do not by themselves promise different CPU isolation or network capacity. These self-managed plans share a hypervisor uplink, so read the selected plan's network terms separately.
Scroll horizontally to see the full table →
| Resource | Measure in your application | Watch during growth |
|---|---|---|
| CPU | Busy request processing and background task duration | Persistent queues or slower processing during simultaneous jobs. |
| RAM | Combined application, cache and database memory | Memory pressure, process restarts and unnecessary worker duplication. |
| Storage | Database size, uploads, logs and temporary files | Free space during imports, deployments and backup creation. |
| Network | Transfer volume and application response patterns | Port capacity and traffic allowance are different plan attributes. |
Your next step
A larger resource allocation does not automatically improve application code or add software administration. Treat the server move as a controlled release with named owners and measurable acceptance checks.
Record runtime versions, database extensions, scheduled jobs, environment variables and outbound integrations. Confirm the destination can support them. Identify configuration that lives outside the application repository so that it is not missed during migration.
Restore a recent copy in an isolated environment and validate logins, writes, uploads and background processing. Keep live payment and email integrations disabled until the test is complete. Compare performance using the same workflow on both environments.
Plan when writes stop, how the last database changes move and when DNS changes. Keep a documented rollback decision point. Retain the previous environment until the new service and its backups have been verified.
Name the people responsible for updates, firewall rules, monitoring and recovery. Review a managed server service if the project needs help with those tasks, and agree the precise application and operating system scope before ordering.
THE DIFFERENCE INSIDE EACH PLAN
Review resources, usage allowances and included services in one table. See where a higher plan gives your project more room as its requirements grow.
Proxmox + KVMEach KVM virtual machine runs its own operating-system kernel. Proxmox provides the management layer; compare CPU, memory and storage for your workload.
Scroll the table horizontally to see more plans.
* Monthly prices are shown. The billing cycle and order total appear in the order summary. Plan resources are subject to the applicable service terms. The network connection is the shared uplink capacity of the physical virtualization host. Read the Unmetered (Fair Usage) traffic policy.
Let’s move your project forward
Choose the right channel for package selection, migration planning or a question about an existing service.
Compare the actual resources and management scope rather than the label. DCHost’s VPS and VDS listings use the same virtual server plan catalogue. Neither the name nor a CPU count alone promises a reserved physical processor. The shared hypervisor uplink is identified separately in the plan table.
No. The network speed shown in these plans belongs to the shared hypervisor uplink. It is not a dedicated connection of that speed for each virtual server. Traffic labelled Unmetered (Fair Usage) is subject to the fair usage provisions in the service terms. Traffic usage and port capacity describe different things; compare them separately in the plan table.
Choose the Turkey location offered for the configuration you are ordering. Confirm the deployment city and availability for that plan before payment. If latency is important, contact us to discuss the target region and a suitable way to test the route from your users’ networks.
These plans are self-managed: you administer the operating system, installed applications, security updates and your own data protection workflow. Technical support is available 24/7; open a support ticket with the service identifier and the problem you observed. English documentation is available. For ongoing software administration, review the separate managed service.
An operating system option does not automatically include every software licence. Review the selected OS, panel licence and IP options in the order summary. Include any paid additions when comparing the total recurring cost of the plan.
Build a backup schedule around how often your data changes, keep copies separate from the running server and test recovery. The published weekly web hosting policy does not define VPS backup retention. For DCHost-assisted backup or restoration, agree the service scope, retention and recovery process through support.
For migration, prepare a copy of your data and test the application before changing DNS; agree any assisted transfer scope with support. For an upgrade, open the service in the customer portal to check available options. Confirm whether the change needs a restart or migration and take a current backup before it begins.
Review the billing period, optional licences, taxes and order total before payment. Check an existing service’s renewal amount in the customer portal; the renewal guide explains the checks. Cancellation and refund eligibility depend on the service and transaction under the refund policy.
Compare plans, choose the required configuration and review the order total.