# We assess and stabilise your MT4/MT5 platform, then leave your team with the monitoring, tooling and runbooks to operate it\.

- Page ID: `home`
- Canonical human URL: https://my-platform-site.kyosls.workers.dev/en/
- Content revision: 2026-09-02
- Intended audience: Broker platform owners, operations leaders and MT4/MT5 engineers.
  - Source: https://my-platform-site.kyosls.workers.dev/en/#ownership

## Summary

We establish a shared, evidence-backed view of the platform, repair agreed priorities through your change process, and transfer the operational capability to your team.

Source: https://my-platform-site.kyosls.workers.dev/en/#overview

## Why teams call

Operational symptoms, platform evidence and team knowledge often live in different places.

### The symptom is distant from the cause

Latency complaints may begin days after the first journal evidence. A measured baseline replaces recollection with a shared record.

### Knowledge is concentrated

Load order, recovery steps and historical decisions need to be available in the client's repository, not only in individual memory.

### The evidence volume is too high for manual review

Server journals, client logs and infrastructure events require tooling that helps engineers find and confirm relevant evidence.

Source: https://my-platform-site.kyosls.workers.dev/en/#problems

## Assess, stabilise, transfer, review

Every phase leaves an artefact the client keeps.

### Assess

Begin with read-only access, interviews and evidence collection. Findings record risk, evidence and the recommended next action.

### Stabilise

Work agreed priorities with the client's engineers, inside the client's approval and change process.

### Transfer

Deliver monitoring, source code, runbooks and training into systems the client controls.

### Review

Review what held, what drifted and which capability the team will take on next.

Source: https://my-platform-site.kyosls.workers.dev/en/#process

## Choose a starting point

Start with the service that matches the question in front of your team; the same evidence-led boundary carries through each path.

Source: https://my-platform-site.kyosls.workers.dev/en/#services

## Capability stays with the client

The goal is a documented platform and a team that can use the agreed runbooks, with external support limited to the model written into the engagement.

- Runbooks, source code and client-specific tooling remain in the client's repository.
- No remediation, uptime, staffing or response outcome is guaranteed unless the applicable agreement states it.
- TICKSTACK is independent of MetaQuotes and does not replace vendor support.

Source: https://my-platform-site.kyosls.workers.dev/en/#ownership

## Verified facts

- [read-only-first] Assessments begin with read-only access.
  - Qualification: Production changes require separate client approval.
  - Source: https://my-platform-site.kyosls.workers.dev/en/#process
- [client-ownership] Monitoring, source code, runbooks and training are delivered into systems the client controls.
  - Source: https://my-platform-site.kyosls.workers.dev/en/#ownership
- [intended-audience] Broker platform owners, operations leaders and MT4/MT5 engineers.
  - Source: https://my-platform-site.kyosls.workers.dev/en/#ownership
- [organization-independence] MetaTrader, MT4 and MT5 are trademarks of MetaQuotes Ltd. TICKSTACK is independent and is not affiliated with MetaQuotes.
  - Source: https://my-platform-site.kyosls.workers.dev/en/#ownership

Contact route: https://my-platform-site.kyosls.workers.dev/en/contact/