Select the operating model
A server specification describes resources. The operating model describes who keeps the environment useful. Choose the tasks your team will handle and the work you want assessed for inclusion in the proposal.
| Workstream | Customer-managed approach | Assisted scope to discuss |
|---|---|---|
| Operating system | Your administrator configures access and updates. | Named setup, patching and maintenance tasks. |
| Terminal applications | Your team installs and validates its programs. | Installation or migration assistance with agreed compatibility boundaries. |
| Monitoring | Your team reviews availability and application signals. | Defined checks, recipients and escalation ownership. |
| Backups | Your team manages copies and verifies restores. | Agreed data scope, schedule, retention and restoration work. |
| Incident investigation | Your team collects evidence and owns the application workflow. | Named infrastructure investigation and cooperation with application owners. |
This is a scope comparison, not a promise that every assisted task is included in each service. Confirm the selected responsibilities in the final offer.
Keep backups and recovery as separate decisions
A backup is useful only if the required data can be restored. Identify which settings, files and databases are covered, where copies are kept and who verifies them. A disk mirror does not provide an independent recovery copy.
Recovery planning also needs the order in which services return. Account-server connections, access permissions and external dependencies must be checked after the files are restored. Agree any recovery objectives and service commitments explicitly.
Give incidents an owner
Describe the affected component, the time of the issue and the safe evidence available. Infrastructure, terminal software, an EA and a broker endpoint can have different support owners. A clear escalation map reduces the time spent asking the wrong party to investigate.
- Host access or resource pressure: identify the infrastructure owner.
- Terminal or program errors: identify the application owner and available logs.
- Integration failures: identify the interface and both endpoint owners.
- Broker-side processing: use the appropriate authorised support route.
Use acceptance checks before the production switch
- Compare the delivered configuration with the written offer.
- Test the intended application set using a demonstration environment.
- Check the approved endpoint and the normal operating workflow.
- Verify disconnect, restart and a representative restoration.
- Record the handover and who accepts changes afterwards.
Apply this scope to Forex VPS, dedicated servers or broker hosting. Prepare a request through the enquiry builder.