Cloud Servers
Compare cloud server CPU, RAM and storage with your application requirements. Choose a listed plan or a custom configuration, then review the location, software and management scope.
“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.”
24/7 technical support
Capacity with a purpose
Cloud server selection begins with the resources your application needs today and the changes you expect later. The listed plans provide a starting point; the configurable option lets you review available CPU, RAM and storage combinations. A cloud label alone does not establish automatic scaling, uninterrupted resizing or a high-availability architecture. Plan those requirements explicitly.
Measure how traffic, stored data and background jobs grow between releases. Choose a starting configuration that covers the current workload, then establish which signal should trigger a capacity review. This gives your team a practical growth plan without buying resources solely on a forecast of future visitor numbers.
Review the busiest user journey before an event, including checkout, search or file processing. Run a representative load test and include connected systems in the result. Discuss available resource changes and their timing early; a plan change should not be assumed to happen automatically when campaign traffic arrives.
Some projects benefit from separating a web application, worker process or database into different environments. Compare the operational overhead with the benefit: each environment needs access control, monitoring and recovery. Check the available networking options and connection requirements before designing communication between servers.
Selection guide
Choose a standard combination when it fits your measured demand. Review the configurable option when the balance of processing, memory and storage is different. Confirm the resulting price, software choices and change procedure at checkout or with the team.
Scroll horizontally to see the full table →
| Workload signal | Configuration question | Operational check |
|---|---|---|
| Memory fills before CPU becomes busy | Would a different RAM allocation fit better? | Check application workers, cache limits and database settings first. |
| Long processing queues | Does the workload need more CPU capacity? | Measure task duration and identify external service delays. |
| Fast-growing files or database | What storage allocation and growth path are available? | Account for temporary data, backups and the resize procedure. |
| Demand varies sharply | When can capacity be changed? | Agree lead time, possible restarts and the billing effect. |
| Service must survive a node failure | What architecture meets the recovery target? | Discuss separate failure domains and data replication; one server is not a complete design. |
Your next step
Document what will change and how you will verify it. Resource flexibility is most useful when it fits a release process, a recovery plan and a budget your team can follow.
Record normal CPU, memory, disk and network use together with application response times. Keep a busy-period sample. Use the same measurements after a configuration change to understand whether the actual bottleneck improved.
Confirm which resources can be adjusted, whether disk changes have restrictions and whether a restart or migration is required. Schedule the work around your application's tolerance for interruption and take a recoverable backup first.
A running instance, a replicated service and a retained backup solve different problems. Describe how much data you can afford to lose and how quickly the service must return, then assess the configuration against those targets.
Include software licences, selected options and any agreed management or backup service in the budget. Review the applicable billing period and new total when changing resources, rather than comparing CPU and RAM alone.
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.
Running a cloud server
Running an application on a cloud server takes more than choosing CPU and RAM. Disk use, maintenance and data recovery also shape the configuration. Planning them together gives you a clearer path from the first deployment to later growth.
An online store during a campaign and an application processing background jobs place different demands on a server. Use the steps below to turn workload measurements into a resource choice and an operating plan.
The web application, database and background workers share resources. Include the operating system and concurrent processes in your memory estimate, and allow for database growth, logs and temporary files when assessing storage.
Look beyond monthly visitor totals. Review CPU and memory use, response times and disk capacity during busy periods. For a new project, use a representative load test to assess the starting requirement.
When an application slows down, identify the bottleneck first. Memory pressure, a full disk and a long-running database query may need different responses. Use those findings to decide whether more resources will help.
Review available changes for your service in the customer portal. Alongside the new price, check whether a restart, migration or partition expansion is needed, and schedule the work for an appropriate maintenance period.
Identify who maintains operating system updates, user permissions, firewall rules and applications. Monitor whether the application responds and whether disk capacity is available, as well as whether the server is running.
Technical support and ongoing software administration can cover different tasks. If your team needs maintenance assistance, define which software and duties a managed service will cover when choosing the service.
File and database backups need to work together. Keep copies independent of the running server, and choose retention, frequency and access permissions around how the application and its data change.
Restore into a test environment to confirm that the data opens and the application runs. For DCHost-assisted backup or recovery, agree the schedule, retention and restore scope for the selected service.
Share your application, current data size and expected usage so we can review the resources and administration you need.
Discuss your cloud requirementsLet’s move your project forward
Choose the right channel for package selection, migration planning or a question about an existing service.
Compare the CPU, RAM and storage shown for each plan with the needs of your application. Confirm the management and location options for the selected configuration. A cloud label alone does not specify automatic failover, replication or a dedicated physical processor.
Open the service in your customer portal to check the available changes. Review the price and whether the change needs a restart, disk expansion or migration. Back up data before a change and check the application afterwards.
Keep independent copies of application files and databases and choose a schedule that matches the rate of change. Agree any provider-assisted backup, snapshot or recovery service for the chosen plan; the web hosting backup policy does not define cloud server retention.
Review the operating system, panel and other software options in the order summary. Available options and licence costs depend on the configuration. Check the billing period and taxes along with those additions before payment.
Technical support is available 24/7 through the customer portal. For ongoing OS and application administration, compare the separate managed server service and agree the required tasks.
Compare resources, service scope and the order total.
