An isolated Linux server environment for applications, databases and websites, with root-access requirements and a configuration you can evaluate.
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.
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 linux vps around a measured workload and a clear operating model.
Node.js, PHP, Python or other compatible Linux workloads that need their own runtime, deployments and background processes.
WordPress, WooCommerce and business websites that will run on a VPS or cloud server with an agreed administration model.
Administrators comfortable maintaining Linux accounts, updates, logs, services and recovery procedures.
The quotation records the available options and the exact supplied configuration.
| Requirement | What to review |
|---|---|
| vCPU and RAM | Choose the published resource size and test the workload |
| Disk | Root volume, database files, uploads and growth headroom |
| Linux distribution | Supported distribution and version confirmed in the quote |
| Access | Root or delegated administration and SSH-key requirements |
| Network | Transfer allowance, addresses and firewall requirements |
| Control panels | Optional software and licence costs reviewed separately |
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.
List the application runtime, database engine and required system packages before choosing a distribution. Confirm supported versions with your software vendor and consider how long those versions will be maintained. A VPS can provide a flexible installation environment, but changing the operating system is an operational change rather than a simple website setting. Document package versions and prepare an application deployment procedure that can be repeated after a restore.
Use named accounts and an agreed SSH access method. Verify the server host key through a trusted channel before the first connection, and protect private keys on administrator devices. Restrict network access where practical and confirm emergency access before changing authentication rules. Root privileges are powerful and should be used with clear ownership. The published resource price does not include management of your users, credentials or application secrets.
Database memory, disk I/O and application queries can determine the useful server size more than the vCPU number alone. Monitor growth and choose backup methods that are consistent with the database. A control panel can simplify some tasks, but it introduces its own licence, update and resource requirements. Review the panel edition and support boundary before installation. Agree who will patch the OS, runtime and application plugins over the life of the service.
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.
Yes, subject to a suitable Linux stack and resource sizing. These workloads use VPS or cloud server configurations. Review caching, database load, updates and backups with your application team.
Root access gives broad administrative control. If your team does not want to handle OS maintenance, request a managed VPS scope and agree which access rights your application operators need.
Specify the distribution and application compatibility requirements in your enquiry. The available image and supported version are confirmed before deployment rather than promised as a permanent list.
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.