Any broker with an API, because the broker connection is yours. Reamer Research's relay sends a strategy's orders to an open-source receiver that places them with your broker; it ships with a paper broker, and you swap in your broker's order calls. Reamer Server, a separate institutional order-management core, talks to your broker through a connector you implement in C, C++, Rust or Go over whatever the broker offers: FIX, REST, WebSocket or its own SDK, starting from a worked FIX 4.4 integration in Go.
Reamer Research: the receiver
Reamer Research's relay sends live orders over a published protocol. The open-source receiver in the examples repository decodes them and ships with a paper broker; swap in your broker's order calls to trade live. Live and paper trading are part of the subscription.
Reamer Server: what a connector does
The connector is a set of functions the server calls. Yours must:
- Send orders, cancels and replaces to the broker.
- Report back fills and order updates, as they arrive.
- Supply the account's state, meaning positions and open orders, on request. The broker is the only record of these; the server keeps none of its own.
- Say whether its trading session is up. While it is down, the server rejects new orders with the reason "venue disconnected" rather than sending them.
Inside those functions, the broker's API is your choice: FIX, a REST or WebSocket API, or the broker's own SDK, as long as your language can call it.
What ships in the Reamer Server kit
- A paper broker, in C++ and Rust, that fills orders in memory. It confirms your server is wired up before you touch a real account.
- A worked FIX 4.4 integration in Go. Its session logs on, keeps sequence numbers, sends heartbeats and reconnects, and its connector turns execution reports into the server's format. One script runs an order to a fill against a simulated venue.
From the example to your broker
The FIX example shows everything a connector needs. You add your credentials and your broker's FIX dialect once per broker, or call its REST or WebSocket API instead.
See How do Reamer Research and Reamer Server fit together? and How do I run several strategies through one broker connection?