By default a LayerOne server is unmanaged: you have root, and everything inside the guest is your responsibility. Managed Services gives LayerOne the published operating-system care responsibilities below.
What it covers
The published scope has three parts on the server where you enable it:
- operating-system patching
- security hardening
- monitoring
The add-on is per server. Enabling it on one VPS does not cover another VPS on the same account.
Price
$25.00 per month per server, metered hourly from account credit. Billing starts immediately with the first hour, so a partial month costs only for the hours during which it is enabled.
Enabling it
On the server's page, Enable Managed Services. It is refused if:
- the account is suspended
- the credit balance is negative
- the server has not finished provisioning
- it is already enabled on that server
Before enabling it for a workload with strict maintenance windows, unusual access controls, or a required response time, open a ticket and confirm the arrangement. The public add-on does not publish a response-time guarantee or a maintenance schedule.
What you still own
Managed Services does not transfer ownership of the application or its data. You still control application releases, application configuration, users, licenses, and data retention.
It is not:
- a backup or snapshot service
- application debugging or development
- a promise that every application-level failure will be detected
- a substitute for your own external uptime checks and alert recipients
See Back up your own data and Monitor your VPS and configure alerts.
If support needs information, include the instance id and the affected service. Do not paste a root password or private key into a ticket. See Handling credentials.
Cancelling
Cancel it on the same page. Managed care and its hourly charge stop immediately; the VPS itself keeps running and continues its normal server billing.