Managed cloud
Managed VPS in black and white: what we do, what you do
“Managed” is not a marketing adjective: it is a list of activities we perform, document and deliver. Here you will find the scope of the base management included in cloud plans, and where our responsibility ends and yours begins.
Server management: what the fee covers
Ongoing activities included in the cloud plans' fee, with scopes and hours defined by the contract.
System updates
Updates to the operating system and base components, planned and applied by us, with announced windows whenever the intervention may have an impact.
Internal operational hardening
We configure VMs following internal hardening practices: access reduced to what is necessary, unneeded services disabled, configurations reviewed periodically. It is a working practice, not a security consulting service.
Monitoring
We keep the machine's availability and resources under watch. When a check flags an infrastructure anomaly, we intervene as per contract.
Backups with restore tests
Daily backup with 14-day retention, verified with periodic restore tests: it is an operational target, and we treat any untested backup as unreliable.
Documented operations
Every activity on your VM is recorded: who intervened, when and what was done. The operations log is part of the service, not an extra.
Scopes and hours set by contract
Incidents and requests have scopes and hours defined in the contract, never support without limits. Whatever falls outside the scope is quoted and approved before being executed.
Operational targets, not SLAs
Managed vs unmanaged VPS: why we only offer managed
A managed VM means the operating system, backups, monitoring and infrastructure incidents are our job, within a written scope. An unmanaged VM would mean handing you root access and leaving patching, system security and abuse handling to you.
The unmanaged offer is not available today: before proposing it we want anti-abuse responsibilities, updates, complaint handling and support defined in writing. Selling root access without these rules would shift the risk onto the customer, and that is not how we work.
If your project requires full autonomy over the machine, let's talk: we assess case by case what we can delegate and within which boundaries.
Who does what on a managed VPS: the responsibility matrix
Delegation only works when boundaries are explicit. This table summarises the standard division of duties on cloud plans; the contract details it.
| Area | We handle | The customer handles |
|---|---|---|
| Operating system | Installation, updates and base configuration | Flags specific needs on packages and versions |
| Backups and restores | Execution, retention and periodic restore tests | Identifies critical data and verifies agreed restores |
| Monitoring and infrastructure incidents | Continuous checks and intervention as per contract | Reports anomalies noticed on the application side |
| Application and code | No intervention, unless additional services are agreed | Development, deploys, application updates and content |
| Access and credentials | Delivery over a secure channel and a documented inventory | Safekeeping of their credentials and management of their users |
| Specialist work | Written quote and documented intervention after approval | Approves scope and costs before execution |
Want to see the scope applied to your case?
Bring us a real project: together we define responsibilities, hours and what stays out, before you sign the offer.