Managed infrastructure. A separate line of business from our platform, and it does not require you to adopt it.
cTrader hosting
We host and operate your cTrader environment — the server side, the integrations and the upkeep — under your own Spotware agreement.
Who this is for
Brokers running cTrader, or adding it alongside another platform, who want it operated by people who have run it before. Particularly brokers whose client base specifically asks for cTrader.
Licence position
Your agreement with Spotware is yours and stays yours. We operate the platform under it. If you move hosting, the licence is unaffected because it was never held by us.
What is included.
- 01
Provisioning and configuration of the cTrader server components and back office.
- 02
Colocated hosting with redundant power and network, and DDoS filtering.
- 03
Monitoring of processes, feed continuity and connection health, alerting to us.
- 04
Backups on a fixed schedule with tested restores.
- 05
FIX and API integration work to your liquidity and payment providers.
- 06
Access for your own staff with the permissions you specify.
- 07
Upgrades coordinated with Spotware releases and applied in your window.
The useful half. Anyone can list what is included.
What is not included.
Stated up front so you are not finding it out during an incident. If something you need is on this list, say so before you sign rather than after.
- The Spotware licence and your commercial relationship with them. That agreement is yours.
- Spotware’s own roadmap or release timing — we operate what they ship.
- Liquidity provider relationships.
- cTrader Copy and cTrader Automate commercial terms, which sit in your Spotware agreement.
Structure, not numbers. The targets are figures and none is verified yet.
How support is structured.
Response targets are numbers, and no number appears on this site until it carries its definition and its measurement. What can be stated now is the shape: what starts the clock, how severity is decided, and what counts as finished.
- What starts the clock
- A ticket raised through the support channel, or an alert from our own monitoring — whichever comes first. If we detect it before you report it, the clock started when the monitor fired, not when you noticed.
- Severity, set by impact not by opinion
- Severity is defined by what a client cannot do: trade, deposit, withdraw, or log in. It is not negotiated per ticket, and it is not lowered because a workaround exists.
- Escalation path
- One queue, and it is engineers rather than a first line reading a script. Escalation is by elapsed time against severity, automatic, and does not require you to ask.
- What counts as resolved
- Service restored and cause identified are two separate states, and the ticket does not close on the first one. You get the cause in writing.
How a migration runs.
- 01
Inventory
Current environment, integrations, and what your Spotware agreement covers.
- 02
Target build
The configuration we will operate, agreed before provisioning.
- 03
Parallel build
Stood up and exercised while the current environment keeps serving.
- 04
Integration
FIX sessions and payment integrations brought up and tested against the real counterparties.
- 05
Rehearsed cutover
Practised with rollback before the real move.
- 06
Handover
Access, monitoring, escalation and runbook, in writing.
Technical detail.
| Components | cTrader server components and back office. |
|---|---|
| Integration | FIX and API to liquidity and payment providers. |
| Backups | Scheduled, with restore testing. |
| Network | Colocated, redundant, DDoS filtered. |
| Upgrades | Coordinated with Spotware releases, applied in your window. |
Pricing.
Figures not published yet. Setup and monthly pricing for this service is a commercial decision that has not been made, and inventing a “from” number would be the first thing on this page that was not true. What is settled is what you get for it — the scope above is the complete list, and the boundary section is the complete exclusion list. When figures exist they go through the same gate as every other number on this site.
Questions that come up.
- Do we need a separate agreement with Spotware?
- You need the agreement you already have, or one you sign directly with them. We operate under it rather than in place of it.
- Can you run cTrader alongside MT5 for the same book?
- Yes. Multiple platforms against one liquidity arrangement is a common configuration and we host both. Reconciling reporting across them is work we will scope honestly rather than wave at.
- Who handles a Spotware-side outage?
- We do the diagnosis, the escalation to Spotware and the communication back to you. What we cannot do is fix their side faster than they can — and we will tell you that is what is happening rather than let it look like ours.
6open items on this page
- Which cTrader components and editions we have operated in production, so the audience claim is specific.
- Response and resolution targets per severity — these are figures and none is verified yet, so no number appears on the page (see /trust/execution for the rule).
- Uptime commitment, and the measurement window it is calculated over.
- Pricing: setup and monthly figures per configuration.
- A dedicated infrastructure enquiry route. The demo form is for the platform and would be the wrong intent here, so the CTA currently points at the support plans page.
- Confirmation of our current data-centre footprint, so the colocation options can be listed by name rather than described.
Next step.
The support arrangement behind this service is the thing worth reading before you talk to anyone, including us.
A dedicated enquiry form for infrastructure work is outstanding — it is on the list above. The demo form is for the platform and would be the wrong thing to send you to.