Managed Servers
Choose server resources and agree the administration tasks your application needs. Review the included panel, software configuration, maintenance and recovery responsibilities together.
“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
People, process and server resources
A managed server combines a server configuration with an agreed set of administration tasks. The useful question is who will maintain each part of your service, from the operating system to the application. Compare resources first, then define the supported software, maintenance process and recovery responsibilities so that your team knows what happens after deployment.
Your team may own website content and customer operations while needing help with the server environment. List the web server, database, control panel and scheduled tasks that require administration. Confirm which tasks the managed service covers and who handles website code, plugins and other application-level changes.
Separate client access, application ownership and support contacts before putting projects on one environment. Discuss resource demand and the effect of a shared maintenance window on each client. A management agreement should describe the supported stack and escalation route, rather than leaving every request to be interpreted after a problem occurs.
Prepare an inventory of software versions, dependencies and recurring jobs. Identify legacy components or custom installations that need a separate review. Agree the migration, acceptance tests and rollback responsibilities alongside ongoing maintenance; a server management service should not be assumed to include every part of an application migration.
Selection guide
Management scope is a service agreement, not a universal feature list. Use these work areas to compare the included tasks with your own team's capabilities. Add application-specific requirements to the discussion before the service starts.
Scroll horizontally to see the full table →
| Work area | Agree with the service team | Keep an owner in your business |
|---|---|---|
| Operating system and panel | Supported versions, updates and access permissions | Approval for changes that affect your application. |
| Web and database services | Configuration work and supported maintenance tasks | Application compatibility, code and database design. |
| Monitoring and incidents | What is monitored, how alerts are handled and escalation | Business impact, application checks and contact availability. |
| Backups and restoration | Data scope, retention, storage and restore procedure | Recovery priorities and validation of restored business data. |
| Custom software | Whether installation and ongoing support are in scope | Licensing, vendor support and application development. |
Your next step
A shared understanding of changes and incidents makes a managed service easier to operate. Keep the service inventory current and include enough application context for each request to be evaluated.
Record domains, applications, versions, licences and dependencies. Add the people who can approve maintenance or provide application access. Review this list after a new deployment so that support is working from the current environment.
Identify when updates can happen and which operations are sensitive to interruption. Establish how changes are requested, approved and checked. Where a restart or compatibility issue is possible, include a backup and a rollback step in the work plan.
Include the affected service, first observed time, error message and recent changes in a support request. Explain whether all users or one workflow is affected. Keep sensitive credentials out of ordinary ticket text and use the agreed secure sharing method.
Clarify who starts a restore, which recovery points are available and who validates the result. Test the business workflow after recovery, not just whether the server starts. Revisit recovery requirements when data volume or business priorities change.
Scroll horizontally to compare every plan. You can also use the arrow keys.
| Compare Servers. | DC MGMT 1 | DC MGMT 2 | DC MGMT 3 | DC MGMT - Wizard |
|---|---|---|---|---|
| CPU | 1 Core | 2 Core | 3 Core | — |
| Memory (RAM) | 2 GB DDR4 | 3 GB DDR4 | 4 GB DDR4 | — |
| Storage | 40 GB SSD | 50 GB SSD | 60 GB SSD | — |
| Network | 10 Gbit | 10 Gbit | 10 Gbit | — |
| Bandwidth | Unlimited | Unlimited | Unlimited | — |
| Control Panel | Included | Included | Included | — |
| CPU | 1 Core | 2 Core | 3 Core | — |
| Memory (RAM) | 2 GB DDR4 | 3 GB DDR4 | 4 GB DDR4 | — |
| Storage | 40 GB SSD | 50 GB SSD | 60 GB SSD | — |
| Port | 10 Gbit | 10 Gbit | 10 Gbit | — |
| 24/7/365 Support |  |
|
|
|
Plan your service
Track services, invoices and support tickets in the customer portal. Identify the service when requesting operating system or application changes.
Plan your service
List the applications and versions to be administered. Assign responsibility for updates, security settings and monitoring as the foundation of regular maintenance.
Plan your service
Plan the impact, backup and rollback steps before a production change. Application development and custom software work need a separate scope.
Plan your service
When reporting an issue, include its start time, errors and recent changes. For a restore, agree the affected data and available recovery point with support.
Let’s move your project forward
Choose the right channel for package selection, migration planning or a question about an existing service.
A managed service adds agreed administration tasks to the server. The listed plans include a panel. Define which operating system updates, security settings, monitoring and restore tasks the service covers; website development and custom application work require their own scope.
Agree the administrator access and software configuration needed for your application when selecting the service. Send change requests through the customer portal so the service, requested action and operational impact can be tracked.
Backup frequency, storage, retention and restoration responsibilities belong to the agreed service scope. The weekly web hosting policy does not automatically apply to a managed server. Identify the data and recovery point you need when arranging the service.
Include the service identifier, application and version, time of the issue and relevant error messages. State any recent change. Technical support is available 24/7; use the ticket for service-specific work and the documentation for account tasks.
Compare resources, service scope and the order total.
