Version 1.4 · 2026-11-20
Effective: 2026-11-20
The French version is the official version. This English text is a courtesy translation.
1. What the service is
A managed dedicated server is a dedicated virtual machine on our infrastructure, for which AdocSys assumes the platform: the allocation, the hypervisor, the operating system, the updates, the monitoring, the backups and the network. You host there whatever you want: sites, applications, databases, mail, containers.
"Managed" describes the platform, not your application. We keep the server online, up to date and backed up. We do not develop, fix or support the software you install on it. That is the same boundary as section 9 of the Terms — and it is what makes the price sustainable.
We do not sell unmanaged servers. Administrator access stays with us: root and SSH are reserved for AdocSys system administrators, unless agreed in writing in the order form.
2. What is included
| Item | What it covers |
|---|---|
| Infrastructure and hypervisor | Dedicated virtual machine, redundant storage, public IP address with reverse DNS |
| System and platform | Operating system and platform agreed in the order form, kept up to date |
| Monitoring | Per-minute application probe, host agent, 24/7 alerts, written and reviewed thresholds |
| Backups | Machine image and off-site replication, daily · 30 days retention on the primary site, 12 months off-site |
| Network and security | Firewall, security tools, baseline hardening, logging |
| DNS | Authoritative zone and records, where the domain is registered with us |
| Access | Root and SSH reserved for AdocSys system administrators, unless agreed in writing in the order form; out-of-band access reserved for operations |
| Support | Platform support, per section 6 |
What we do not touch without telling you: your content, your databases, your email. Operational access exists to diagnose a fault and restore a backup, not to intervene in your data.
3. Included capacity
The order form sets the four figures that matter:
- virtual processors and memory;
- usable disk;
- number of hosted sites (vhosts);
- number of mail domains and mailboxes.
Traffic. Unmetered, unless the order form states otherwise. It must stay proportionate to the price paid and the hardware provided, and must never affect the other clients who share the same links. If it does, we may impose a limit.
How it is counted. A site is a vhost with its database. A mail domain is a domain with its mailboxes, aliases and archive. An overage is billed at the order form's rate, the following month and never retroactively — and never without writing to you first.
What triggers an upgrade — the thresholds are written to be verifiable, not to be argued:
| Signal | Threshold |
|---|---|
| Disk | more than 80% for two weeks, or more than 90% at any time |
| Memory | less than 20% available, or sustained memory pressure (PSI) |
| PHP-FPM | recurring saturation (max children reached) |
| MariaDB | connections near the configured maximum, or excessive SQL queries, poorly written or poorly indexed |
| Backup | the backup window overruns the maintenance window |
| a queue that builds up without draining |
None of these signals cuts the service. They start a conversation, with the figures in hand, before it becomes an incident. It is the house rule: a capacity conversation in November is a plan; in January it is an incident.
4. What is not included
- your applications, your code, your integrations and their databases;
- support for your users and your clients;
- development, application fixes, migrations and content, unless under a separate order form;
- third-party licences, domain names and resold services;
- your computers, phones, printers and networks;
- recovering data you deleted yourself.
All of the above is quoted at the labour rate in force, on written authorisation and before the work is done.
5. Software updates
The system, the platform and the tools we provide are kept up to date by AdocSys. What you install is yours, and so is its updating.
You undertake to update any software you install on the server within the following deadlines:
| Type of fix | Deadline |
|---|---|
| Actively exploited vulnerability (CISA KEV catalogue) | 7 days |
| Critical CVE (CVSS 9.0 or higher) on an internet-facing service | 14 days |
| Other critical or high CVE (CVSS 7.0 to 8.9) | 30 days |
| Medium CVE (CVSS 4.0 to 6.9) | 90 days |
An internet-facing service is anything that answers from outside: portal, API, control panel, VPN, mail.
These deadlines are ceilings, not targets. Patch as soon as the fix is published, and without waiting for the limit on a vulnerability already being exploited. Subscribe to the news feeds of the software you use: that is what warns you before the incident, not after.
If a fix is not applied within the deadline, we may report it to you, restrict access to the vulnerable service, or stop it, depending on the risk. We can also apply it for you, at the hourly rate, on request. A fix is a vendor update: it is not development, and it is not included.
6. Support
- Hours: Monday to Friday, 8:00 a.m. to 8:00 p.m. Eastern, except statutory holidays.
- Channels: support@adocsys.net, the website form, or 1 877 749-9579.
- Response times: two business days for an ordinary request; four hours during business hours for a service that is down.
- Emergency — evening, weekend, statutory holiday: at the emergency rate in force. We answer if you reach us; it is never included.
- Scope: the platform — system, control panel, network, DNS, backups. Not your application, not your users.
Support is a scope, not a number of hours. We do not guarantee a resolution time, only a response time.
If you resell hosting to your own clients, they call you, not us. The support we owe you covers the server; first-line support for your clients is yours. This is written in the order form.
7. Service level
Target: 99.9% per month, measured per minute, 24 hours a day. Credits of 25%, 50% or 100% of the monthly fee depending on measured availability, claim within 30 days. The binding numbers are in Annex A of the Terms and Conditions; the "Service Level Agreement (SLA)" article of the knowledge base explains them.
Two conditions, without which the service level does not apply: monitoring and alerting stay active, and local machine backups stay active. Without them, we can neither detect the fault nor return the server to service.
8. Data, access and exit
Your content belongs to you. We use it to provide, protect and support the service, and for nothing else.
- Export: the machine backup is provided free of charge on request, within 30 days of the end of the service. After those 30 days, extracting it from the second site is work billed at the hourly rate in force. Any other export or manual work is billed at the same rate.
- Retention: content kept 90 days after the end of the service, then destroyed. Backup copies expire on their cycle (30 days on the primary site, up to 12 months off-site).
- No exit penalty, no proprietary format.
9. Upgrades and downgrades
- Upgrade: the pro-rated difference, with no setup fee if the platform stays the same.
- Downgrade: at renewal only, never mid-term.
- Capacity review: once a quarter, in writing. Three lines are enough: what was added, what is left, and what is coming.
10. What this document does not do
It sets no price, no term and no configuration: those three things are in the client's order form. It does not replace the Terms and Conditions, which remain the contract.
Order of priority in case of conflict: order form → this definition → Terms and Conditions.
AdocSys · 657 route Marie-Victorin, Verchères, Quebec J0L2R0, Canada
support@adocsys.net · 1 877 749-9579 · adocsys.com