Broker support

Trust-first broker connect copy, not vague integration bragging.

The broker section has one job: explain how Glitch Trade connects, what permissions are involved, and why the user should trust the model. The point is clarity, not buzzwords.

Trust model: We never trade on your behalf. cTrader uses read-only OAuth. Other brokers: password exchanged once for a refresh token, then discarded.

Read-only OAuth

cTrader

Supported path

Most trust-friendly path. You authorize a read-only connection, we track the account, and you keep control of execution decisions.

Best starting point for users who want the cleanest permissions story from day one.

Credential exchange once

TradeLocker

Supported path

Username and password are exchanged once for a refresh token, then the password is discarded.

Good when you want the Glitch Trade dashboard but your broker flow is not on cTrader.

Live integration in progress

DXtrade

Supported path

Same credentialed model as TradeLocker: password exchanged once for a refresh token, then discarded.

Included in the roadmap and marketing surface now because it is part of the locked broker story.

Bridge any Meta broker

MT4 / MT5 via MetaApi

Supported path

MetaApi.cloud acts as the bridge so MT brokers such as ICMarkets, Pepperstone, FTMO, or MFF can feed into the same tracking model.

Useful when you need MT portability rather than a broker-native dashboard.