Map the applications that run the business
Broker hosting is a component-level infrastructure project. Start with the applications and the business workflows they support, then decide where each component runs. A web application, database and connectivity service may have different load profiles and support owners.
| Layer | Infrastructure question |
|---|---|
| Client applications and CRM | Where are records stored and which interfaces change account status? |
| Platform components | What environment and access does the authorised arrangement require? |
| Databases | What storage, backup consistency and recovery sequence are needed? |
| Integration services | Which endpoints, service identities and counterparties must remain reachable? |
| Monitoring and operations | Who sees failures and who owns escalation for each layer? |
Separate access and failure domains
A single machine may simplify an initial deployment, but its applications share a host failure. Decide whether public-facing services, databases and administrative tools need separate environments or network boundaries. Match access rights to the tasks each role performs.
Record the supported route between components, which interfaces are public and which administrative paths are restricted. Confirm the responsibilities of infrastructure and application teams in the operating scope.
Validate a workflow across the interfaces
- Choose an agreed test client or demonstration workflow.
- Exercise account creation and the permitted operational changes.
- Check the resulting application records and reconciliation process.
- Observe a controlled dependency failure and its escalation route.
- Restore the required data and applications in their documented order.
Acceptance should follow the complete workflow, not only whether a server can be reached.
Plan an operating handover
Keep an application inventory, component owners, safe incident evidence and a maintenance plan. Define how changes are approved and who checks the result. Backup retention and a usable restoration path should be agreed before the deployment supports production work.
For platform-specific scope see MT4 White Label and MT5 White Label. For hardware and recovery topology use broker server planning.