Dedicated hardware with a scoped OS administration and management engagement, separating hardware service boundaries from application ownership.
Start with a plan below, or talk to us about a custom setup.
Starting monthly rate; hardware configuration and availability confirmed in the quotation.
Monthly rate; commitment confirmed in quotation
Applicable taxes, software licences, migration, backups and management unless expressly included.
Choose managed dedicated servers around a measured workload and a clear operating model.
Organisations that need exclusive hardware and a documented process for OS maintenance, escalation and operational handover.
Applications with databases, scheduled jobs or network dependencies that need an agreed administration checklist and change approvals.
Teams that retain business application responsibility while delegating defined server administration tasks.
The quotation records the available options and the exact supplied configuration.
| Requirement | What to review |
|---|---|
| Hardware | Exact processor, RAM, disk and connectivity quotation |
| Infrastructure boundary | How hardware issues are reported and handled |
| OS administration | The installations, updates and configuration tasks covered |
| Monitoring | Named resource and service checks, recipients and escalation |
| Backup options | Jobs and restore tests included only when agreed |
| Exclusions | Application development, vendor issues and unlisted services |
Separate the core service from work and software that need an additional agreement.
The server configuration or professional service described in the quotation. Confirm access, operating system and the agreed deliverables.
Migration, backup administration, monitoring, management and additional software need a separately agreed scope and price.
Confirm taxes, setup charges, licensing, commitment, renewal and cancellation. Availability, workload location and support commitments belong in the quotation.
A dedicated configuration and a management service describe different responsibilities. Ask for the complete hardware specification and the process for reporting infrastructure faults. Separately define OS installation, updates, configuration changes and remote access administration. A management fee does not establish a replacement time for physical equipment or an application uptime commitment. These service boundaries belong in the approved quotation and operational documents for the actual supplied environment.
Physical server updates and configuration changes can affect storage, boot behaviour and remote administration. Keep a current inventory, identify approval contacts and establish how a maintenance window is chosen. Prepare recovery information before changing important components. Application owners should define acceptance tests and participate when their software may be affected. A predictable maintenance procedure is more useful than a broad claim that every issue will be handled automatically.
If backup administration is included, identify the protected datasets, job ownership, retention and restore test method. Give the operating team enough application context to distinguish a server symptom from a business problem. Document escalation contacts, access approvals and the information required to investigate an incident. Monitoring coverage and response targets are confirmed in the agreement; they are not inferred from an always-visible website or the word managed.
The management proposal lists the environments and tasks that CloudLelo will administer. It should identify monitoring checks, maintenance approval, patching windows, backup administration and incident escalation. Your team retains responsibility for application changes, business data, access approvals and decisions about acceptable interruption. An agreed scope is essential: server management does not automatically include application development, software vendor support or unlimited incident work.
A task is assigned to CloudLelo only when it appears in the agreed management scope.
| Task | Customer / self-managed | Scoped CloudLelo management |
|---|---|---|
| Configuration | Define and administer the environment | Perform agreed configuration tasks |
| OS / account updates | Plan, test and apply required changes | Apply agreed changes in approved windows |
| Monitoring | Select checks and respond to alerts | Operate the specified checks and escalation |
| Backup administration | Arrange jobs, retention and recovery testing | Administer the agreed backup jobs and restore tests |
| Applications and data | Own code, data and business validation | Application work only where explicitly included |
| Support scope | Provide authorised contacts and useful incident detail | Follow the agreed channels and service boundaries |
Deployment dates, service commitments and acceptance criteria are agreed for your project.
List applications, versions, dependencies, usage and authorised contacts. Identify protected data and the business owner who can validate deployment.
Confirm resources, software, access, transfer, fees and the administration scope. Record commitments and exclusions before approving the quotation.
Agree migration or deployment, backup checks and acceptance tests. Define the rollback decision and retain source access until handover criteria are met.
Document credentials, ownership and escalation contacts. Review resource use, maintenance and recovery arrangements as the workload changes.
Understand the configuration and responsibilities before requesting an order.
Dedicated entry cards are starting benchmarks. The exact CPU, memory, drives, RAID and connectivity are agreed in the quotation, together with availability and licensing.
Your application owner or software vendor remains responsible unless application support is specifically included. The management scope should define coordination and any additional work that can be requested.
Backup administration and storage are separately reviewed. The quote identifies any included jobs, retention and restore work rather than assuming every managed server has the same backup policy.
The quotation identifies resources or subscriptions, selected operating work, taxes, licences and commercial commitments. Consulting and provider consumption charges are reviewed separately.
Describe the application or provider, current setup, users, data size and intended change. Avoid passwords, private keys and confidential business records.
Confirm protected data, frequency, retention, storage location and restore responsibilities separately. Provider retention features do not automatically establish an independent backup arrangement.
The approved scope lists tasks, channels, escalation and maintenance responsibilities. Any support hours or response commitments must be agreed for the service.
Changes depend on availability, software and commercial commitments. Review potential interruption, data, licences and costs before approving a resource or subscription change.
From a new server to an existing application migration, start with your workload and leave with a clearly defined scope.