Virtual server configurations for business websites, applications and databases, with guidance on resource sizing, migration and management.
Start with a plan below, or talk to us about a custom setup.
Monthly virtual resources; additional software and operating services are separately scoped.
Monthly rate; commitment confirmed in quotation
Applicable taxes, software licences, migration, backups and management unless expressly included.
Monthly virtual resources; additional software and operating services are separately scoped.
Monthly rate; commitment confirmed in quotation
Applicable taxes, software licences, migration, backups and management unless expressly included.
Monthly virtual resources; additional software and operating services are separately scoped.
Monthly rate; commitment confirmed in quotation
Applicable taxes, software licences, migration, backups and management unless expressly included.
Monthly virtual resources; additional software and operating services are separately scoped.
Monthly rate; commitment confirmed in quotation
Applicable taxes, software licences, migration, backups and management unless expressly included.
Choose cloud servers around a measured workload and a clear operating model.
Teams running web applications, APIs or internal tools that need an operating-system environment and defined virtual resources.
Businesses comparing CPU, memory and storage for a site with variable traffic, rather than selecting a plan from visitor counts alone.
Developers separating staging and production, or organisations that need a distinct environment for a database or integration.
The quotation records the available options and the exact supplied configuration.
| Requirement | What to review |
|---|---|
| Compute | vCPU allocation, processor characteristics and peak utilisation |
| Memory | Application working set, database cache and headroom |
| Storage | Capacity, I/O behaviour, disk growth and recovery needs |
| Network | Transfer allowance, port speed, IPv4 and access requirements |
| Operating system | Application-compatible distribution and licensing |
| Location | Available hosting location confirmed in the quotation |
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.
Record CPU peaks, memory pressure, database activity and storage growth over a representative business period. A web application can need more memory than a static site with similar traffic. Start with an environment that leaves useful headroom, then test the application under realistic requests. CloudLelo can review your measurements and configuration requirements; the result is a proposed resource specification, not a guaranteed visitor capacity.
Disk capacity, disk performance and network transfer solve different problems. List database files, uploads, logs and temporary workspaces before choosing storage. For transfer, estimate downloads, API traffic, replication and backup movement. Ask for the available transfer allowance and treatment of additional usage. A backup stored elsewhere also needs network capacity; the server resource card does not establish a retention policy or an unlimited transfer entitlement.
More CPU or RAM may require a restart, a changed server configuration or a move to another environment. Check application compatibility, disk expansion and any address or DNS changes before an upgrade. Keep an application-consistent backup and define validation steps. For a business that needs faster recovery, review backup choices and a recovery environment separately. Flexible resources are useful, but they do not replace a tested continuity plan.
A self-managed configuration gives your team responsibility for the operating system and application environment. Plan how you will patch software, manage access, monitor capacity and respond to incidents. CloudLelo management and backup administration can be requested as additional scoped services. Confirm the boundary between infrastructure support, operating-system administration and application support; none should be assumed from a resource specification alone.
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.
No high-availability architecture is implied by a single server configuration. Discuss application replication, load balancing, recovery requirements and the available platform design before treating a workload as redundant.
Tell us where your users and business systems are located. Available deployment locations and the treatment of stored data are confirmed in the quotation; office addresses are not server-location promises.
Starting resource prices are for configuration planning. Operating-system administration, monitoring and backup work need a defined scope. Compare the managed cloud option if you want us to review those tasks.
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.