Draw the boundary between host and operator
A hosting company can supply infrastructure without administering the trading platform. A platform provider can manage configuration while a separate supplier controls the machine. Record both boundaries. The brokerage should know who can investigate a failed login, who can change a network rule and who can recover the service.
Start with the actual platform inventory. Include component versions, server roles, connected services and the access needed by each support party. For existing installations, verify the inventory against the running environment rather than copying an old diagram.
Compare hosting proposals by responsibility
| Responsibility | Clarify the owner | Ask for a practical demonstration |
|---|---|---|
| Infrastructure availability | Host and escalation route | How an unavailable machine is replaced |
| Platform configuration | Authorised platform operator | How an approved setting change is recorded |
| Data protection | Backup and restore operators | How application state is recovered and checked |
| Observability | Monitoring and incident owner | How an alert becomes an actionable incident |
A proposal can divide these responsibilities in several ways. The requirement is clarity and a workable escalation path, not an assumption that one party must perform every task.
Match placement to the paths that matter
Measure client access, provider connectivity and administrative access separately. A location close to one dependency may be less suitable for another. Regional access and resilient operation should be justified by the actual users, counterparties and recovery requirements.
Validate the workload with the intended integrations and background tasks. Keep a baseline of resource behaviour and user-visible symptoms so later changes can be evaluated against evidence. A hardware upgrade without a baseline makes it difficult to tell what improved.
Choose the platform-specific plan
Use the MT4 hosting review for an existing MT4 estate with established symbols, groups and integrations. Use the MT5 hosting plan when reviewing MT5 component placement and access paths. Do not carry assumptions from one environment into the other without checking them.
The handover should include an owner map, approved access, monitoring coverage, maintenance procedure and restoration evidence. For MT4 White Label or MT5 White Label, confirm which hosting responsibilities are already supplied within the platform arrangement before purchasing overlapping services.