FAQ · Reamer Research and Reamer Server: what they are and who they fit
How long does integration take?
For Reamer Research, a couple of minutes to a first run: install the Python package or include the C++ header, write a strategy as a plain function or a class and call `backtest`. For Reamer Server, an uncut recording shows Claude Code, working only from the kit documents, integrating it through to a simulated fill in about 19 minutes; the kit puts a person's first simulated trade at a few hours. Going live at a real broker then follows your broker's own onboarding: fitting the connector to its protocol and, where it asks, its certification. That is done once per broker, and every strategy shares the connection.
For Reamer Research, a couple of minutes to a first run: install the Python package or include the C++ header, write a strategy as a plain function or a class and call backtest. For Reamer Server, an uncut recording shows Claude Code, working only from the kit documents, integrating it through to a simulated fill in about 19 minutes; the kit puts a person's first simulated trade at a few hours. Going live at a real broker then follows your broker's own onboarding: fitting the connector to its protocol and, where it asks, its certification. That is done once per broker, and every strategy shares the connection.
Reamer Research: a first run
- Install.
pip install the wheel from the kit, or add include/reamer_research.hpp with CMake find_package, pkg-config or by hand. - Write a function. It receives a window of bars and returns an order, or nothing. Brackets attach in the same call.
- Run and inspect.
backtest prints the summary, writes the JSON report and opens the visual trade diagnostics tool, with every closed trade charted on its own bars.
The whole quickstart, an ATR band reversion with a bracket on every entry, is 14 lines of Python. It is on the Reamer Research page in Python and C++.
Reamer Server: the recording
The recording starts from a fresh copy of the kit, with no source code and no earlier exposure. A wall clock runs throughout, and the elapsed time is the measurement. It was recorded against version 4.2.1 and is sped up, returning to normal speed at the end. In about 19 minutes the agent built its own gate and broker connector in C++, modelled on the kit's Go example, including a FIX 4.4 session, and ran orders through to a fill against the kit's simulated venue. It is on the Reamer Server page.
Connecting to your data and your broker
Both are ordinary API connections, and you keep full control of each:
- Data for Reamer Research is one fetcher call against your own Alpaca or Databento account, or bars from any other source passed in as arrays. See Where does the market data come from?
- Live trading with Reamer Research goes through the open-source receiver. Its broker is a class with three methods,
on_order, on_cancel and on_replace; the kit's paper broker fills them in memory, and you swap in your broker's order calls. - A Reamer Server connector is a short table of functions (submit, cancel, replace, account state and updates) written in C, C++, Rust or Go. The kit's paper skeleton is 103 lines, and its worked FIX 4.4 integration in Go shows a full session. Your gate's rules and your broker's own onboarding complete the setup.
See Which brokers can I connect to?
Next questions
Can I paper trade before going live?Yes, with either product on its own. Reamer Research's relay sends a strategy's orders through the open-source receiver to your broker's paper or demo account. With Reamer Server, a separate order-management core for firms, point your connector at the paper account instead. The licence allows paper and live trading for both. The Reamer Server kit's in-memory paper broker is a wiring check: it fills every order instantly at a made-up price to confirm your server is connected correctly.What results and metrics does a run produce?A Reamer Research run produces 31 summary metrics, every closed trade, every fill and every order with its outcome, as one schema-versioned JSON document. The Python package and the C++ header return all of it, the same as the C interface.How do Reamer Research and Reamer Server fit together?They are two separate products for two different jobs, and each is complete on its own. Reamer Research is a Python and C++ backtesting engine that also trades live: its relay sends the orders a strategy returns to a receiver you run, which places them with your broker. Reamer Server is an institutional order-management core that trading firms build their own live trading infrastructure around. With both, you choose the market data vendor and the broker.Which brokers can I connect to?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.
Every answer here restates the documents that ship in the kit,
which are authoritative. All questions.