Brokers

Connect the broker you already use. Authorize only what your agents need.

Glitch Executor is tooling, not an asset manager. Each integration requests only the scope your agents need to run, and we surface the trust posture in the dashboard so you always know what we hold.

Trust posture OAuth, read-only Credential exchange once, then discarded Cloud-bridged via a third-party API
cTrader

cTrader

Read-only OAuth

OAuth · safest

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.

Open a cTrader account (partner link)
TradeLocker

TradeLocker

Credential exchange once

Credentialed once

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

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

DXtrade

DXtrade

Live integration in progress

Credentialed once

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.

MetaTrader 5

MT4 / MT5 via MetaApi

Bridge any Meta broker

Cloud-bridged

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.

Compatibility

Which prop firms each broker bridges

Picking a broker is usually a downstream decision once you've chosen the firm. If you're coming the other way (you already have a cTrader account, who funds it?), here's the cross-reference. Updated alongside the firm-rule catalogue.

Cross-references the catalogue. See the side-by-side rule comparison for the rule values per firm.

Connect a broker. See your accounts in one place.