Appearance
Are you an LLM? You can read better optimized documentation at /accounts/self-host.md for this page in Markdown format
Self-Host Providers
Every account TTMT trades on reaches your broker through a provider — the plumbing that carries orders and price data between TTMT and MetaTrader. Almost everyone uses the same one, and you don't have to think about it. This page explains the choices, why one is the default, and the handful of things that behave differently on the limited-preview alternatives, so you can tell whether a difference you're seeing is your setup or your provider.
Limited preview
Self-host providers are in limited preview and are enabled per account on request. Availability, behavior, and naming may change before general release. Contact support if you'd like to take part.
The three providers
| Provider | Who it's for | Status |
|---|---|---|
| MetaAPI Cloud | Almost everyone. The default and recommended path. | Generally available |
| Self-Host Terminal | Eligible accounts running against a self-hosted terminal. | Limited preview |
| Self-Host Client | Eligible accounts on the self-host client path. | Limited preview |
MetaAPI Cloud is what you get unless you were specifically enrolled in the preview. TTMT connects to your broker through MetaAPI's cloud, and broker-managed features work wherever your broker supports them. If you're not sure which provider an account uses, open the account's details dialog — the provider is listed there.
The two self-host providers are a private preview. They exist for a narrower set of accounts and are guarded so that, if the pieces they depend on aren't in place, they fail closed — the account simply doesn't come up on that path rather than trading in a half-configured state. That's deliberate: a trading connection should never be "sort of" connected.
One connection per account, always
Whatever the provider, TTMT keeps exactly one shared streaming connection to your broker per account. Your open positions, live prices, and order flow all ride that single link — TTMT never opens a second, competing connection to the same account, because a broker only permits one and a second would fight the first.
You don't manage this. It matters only because it explains a few things you'll see elsewhere in the docs: connection health is judged per account, a reconnect rebuilds that one link, and market-data freshness is a property of that single feed. See Connecting an account for how health is reported.
What behaves differently on self-host
Most trading behaves identically across providers — sizing, layered entries, TP handling, breakeven, and Risk Limits all work the same. The differences are narrow and specific.
Broker-managed trailing stops
Trailing stops differ by provider
On MetaAPI Cloud (and broker-supported setups), a trailing stop can be handled broker-side where your broker supports it — it keeps adjusting even if TTMT's link briefly drops. The gateway-backed self-host path deliberately does not support broker-managed trailing: rather than half-arm it, it skips activating that feature. If you rely on trailing stops, keep them on a Cloud account, or lean on breakeven instead, which is not affected. This is separate from ordinary breakeven behavior.
Market-data details
Self-host providers can surface market data and candle history slightly differently from Cloud — for example, how quickly a fresh feed settles after a reconnect, or which historical candles are available for a chart. These are cosmetic-to-diagnostic differences, not changes to how trades are sized or executed. If an open-trade chart looks sparse on a self-host account, that's the provider, not a lost trade.
The self-host upgrade path (eligible demo accounts)
Some eligible cloud demo accounts can be upgraded to a self-host provider from the dashboard. It's a real move of the account onto the self-host path, not a setting you flip back and forth, so it comes with conditions.
Limited preview
The upgrade path is part of the same limited preview. If you don't see it offered on an account, it isn't enabled for you yet — contact support if you'd like to take part.
Before you can upgrade:
- The account must be flat — no open positions and no pending orders. Close or cancel everything first. TTMT checks this before it will proceed.
- Your configuration and history are preserved — your settings, channel assignments, symbol mappings, and trade history carry across. You are not starting from a blank account.
Know before you commit:
The upgrade is one-way in the UI
Once you upgrade an account to self-host, there is no dashboard button to move it back to Cloud. Returning an account to the Cloud provider requires support. Because of that, upgrade a demo account you're comfortable keeping on the new path — not one you'll want to flip back tomorrow.
If the upgrade can't complete — a credential probe fails, or a required piece isn't in place — the account stays where it was rather than landing in a broken state. That's the same fail-closed principle the self-host providers use everywhere.
Which provider am I on?
If you never asked for the preview, you're on MetaAPI Cloud — and everything in the rest of these docs applies to you without caveats. If you did enroll, check any account's details dialog to confirm its provider, and treat the trailing-stop and market-data notes above as the only behavior that changes.