Separate platform administration from host administration
An operator able to administer a server does not automatically have the right to configure every platform function. Record platform access, software provision, operating-system administration and external-service permissions as separate entries.
For an existing MT4 environment, document the established integrations and operating procedures. For MT5, review the platform roles and topology available under the proposed arrangement. The hosting plan must reflect that specific environment rather than a generic list of virtual-machine resources.
Review the operational handoffs
| Area | Agree before deployment |
|---|---|
| Software and rights | Who supplies the platform components and permitted deployment arrangement |
| Host operations | Who patches, restarts and controls privileged access |
| Connectivity | Who configures and supports each external adapter or endpoint |
| Observability | Who receives host, platform and dependency alarms |
| Recovery | Which data/configuration is protected and who validates restoration |
Record change windows and escalation contacts for each boundary. An incident may require both the hosting operator and an application or connectivity provider to act.
Use platform workflows to accept the hosting result
Illustrative handover: a replacement hosting environment passes a basic availability check. Before acceptance, the team also checks representative client access, authorised management operations, connected data and reporting workflows, and the restoration procedure.
This distinguishes a functioning host from a usable brokerage environment. Keep the resource assumptions, configuration baseline and test evidence together. If growth or a new integration changes the workload, revisit the hosting design using measured activity rather than assuming the original server package remains suitable.