Dedicated Servers
Choose a physical server for your workload. Compare processor models, memory and disk configurations, then arrange the deployment location, software licences and operating requirements.
“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.”
Monthly prices. Your configuration total appears in the order summary.
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 physical server for your workload
A dedicated server lets you select a physical machine for your application environment. Processor generation, memory capacity, disk layout and remote access all affect the choice. Start with the workload you need to operate and compare the listed configurations as complete systems, including software licences, deployment location and the administration your team will provide.
Rendering, batch jobs and busy application services can use processing capacity for long periods. Check whether the software benefits from more cores, higher per-core performance or additional memory. Compare the actual processor models and test a representative job when possible; two machines with similar core counts can behave differently.
Database work depends on memory use, query patterns and disk behaviour together. Estimate the active dataset, write volume and future growth before choosing a disk arrangement. Leave space for indexes, temporary work and maintenance. Plan a separate recovery copy regardless of whether the configuration offers a RAID option.
A physical machine may suit a project with a specific operating system, hypervisor or licensing requirement. Check software compatibility, installation options and the access needed to administer the machine. If you plan to create multiple guest environments, include their combined resources, network design and recovery process in the configuration review.
Selection guide
The catalogue shows individual hardware configurations. Read values that are supplied for each machine and discuss any unspecified requirement before ordering. Additional hardware, IP addresses and software depend on the options available for that configuration.
Scroll horizontally to see the full table →
| Component | Question for your workload | What to confirm |
|---|---|---|
| Processor | Does the application favour core count or per-core performance? | Exact model, physical cores and relevant software compatibility. |
| Memory | How large is the active dataset and combined process footprint? | Installed memory and available expansion for the machine. |
| Storage and RAID | What read, write and recovery behaviour do you need? | Disk types, usable capacity and any selected RAID configuration. |
| Network and addresses | How much data moves and how is the service exposed? | Port capacity, Unmetered (Fair Usage) traffic terms and assigned or additional IP options. |
| Administration | Who will install, update and recover the environment? | OS, licences, hardware console access and management scope. |
Your next step
Hardware selection is one stage of a server move. Agree the configuration and delivery schedule, then prepare a migration plan that protects data and lets the team validate the new environment.
List operating system requirements, control panel choices and licensed applications. Confirm that the hardware and installation options fit those needs. Include application vendor requirements before placing the order, particularly for a custom hypervisor or older software.
RAID may help a system continue through certain disk failures, but it does not replace a backup. Keep copies independent of the machine, define retention and test how files or databases return after accidental deletion or corruption.
Review the available console and recovery access for the chosen machine. Set administrator permissions and firewall rules deliberately. Keep an access recovery procedure so that an incorrect network rule does not leave the team without a way to diagnose the system.
Install the environment, copy data and test the application before changing production traffic. Plan the final write freeze and rollback decision. Check the recurring order total with selected licences and options, then document the live configuration for future maintenance.
Preparing physical infrastructure
A dedicated server makes the selected physical machine available to your project. Compare the processor model, memory requirement and disk layout with the way your application actually uses resources.
Installation, administrator access and data migration follow the hardware choice. Plan these steps alongside the delivery schedule so you can verify the new environment before directing production traffic to it.
Per-core performance, software compatibility and memory capacity matter alongside processor count. Confirm physical-core and logical-thread totals separately for the configuration you select.
Choose disk types and usable capacity around database activity, file access and growth. Review how the selected RAID arrangement affects usable space and behaviour during a disk failure, rather than relying on the sum of disk sizes.
Operating system access and a remote hardware console, where offered, serve different purposes. During installation, identify the administration methods, recovery access and authorised users available for the selected machine.
RAID can help with certain disk failures; it cannot by itself recover accidentally deleted data or a damaged application. Keep backups independent of the machine and test that files and databases can be restored together.
Once the operating system, panel licence and application dependencies are ready, test the new environment with a copy of your data. Check web, database and email services individually where they are part of the move.
Plan when writing will pause for the final data transfer and when DNS will change. Keep the previous service available until the new environment is verified, and agree the conditions for a rollback with your team.
Share your workload, software requirements and current hardware so we can review a suitable dedicated server configuration.
Discuss your hardware needsTHE 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.
Entry and high-capacity configurations from the EKO, V2 and V4 families. The pricing list above contains every model.
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. 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.
A dedicated server allocates a physical machine to your service. A VPS or VDS is a virtual machine on a host. Choose physical hardware when the workload or configuration requires it, and compare CPU model, memory, disks and management scope rather than the product name alone.
Confirm the configuration, deployment location and installation requirements when arranging your order. The custom configuration option lists ComNet DC / Turkey; this does not establish availability for every model. Delivery depends on the selected hardware and preparation, so agree the schedule before planning a production move.
No. The operating system runs your applications; a hosting panel helps manage sites; IPMI or a remote hardware console provides access to the physical server. Review which access and software options come with your selected configuration, including licence and additional IP charges.
Do not apply the web hosting backup policy to a dedicated server. Plan independent backup storage and a recovery schedule for your data. If you require DCHost-assisted backup or restore work, agree the storage, retention and recovery scope for that service. RAID alone is not a backup.
Technical support is available 24/7 through the customer portal. Include the server identifier, when the issue began, any error messages and the access methods affected. A response or hardware replacement commitment must come from the terms agreed for the selected service; a general uptime figure is not a replacement schedule.
Review the billing period, setup work, operating system and panel licences, IP options and taxes for the selected configuration. Check renewal amounts in the customer portal. Cancellation and refunds follow the applicable service policy.
Choose hardware, then arrange the location and operating requirements.
