FAQ · Reamer Research and Reamer Server: what they are and who they fit

Is there a steep learning curve?

Not for the integration. Reamer Research installs as a Python package or one C++ header, and a strategy is a plain function or a class, so a first backtest runs in a couple of minutes. For Reamer Server, the kit documents are enough for a coding agent: in an uncut recording, Claude Code working only from the kit integrated it in about 19 minutes. What still takes your judgement is the trading itself: your strategy, your data, your gate's rules and your broker.

Not for the integration. Reamer Research installs as a Python package or one C++ header, and a strategy is a plain function or a class, so a first backtest runs in a couple of minutes. For Reamer Server, the kit documents are enough for a coding agent: in an uncut recording, Claude Code working only from the kit integrated it in about 19 minutes. What still takes your judgement is the trading itself: your strategy, your data, your gate's rules and your broker.

Why it looks steep, and why it isn't

Reamer Research is used from Python or C++. You install the package or include the header, write a function that receives a window of bars and returns an order, and call backtest. The run prints a summary, writes the JSON report and opens the visual trade diagnostics tool.

Reamer Server is an engine with a C interface that you link into your own program, and Reamer Research from a language other than Python or C++ means wrapping its C ABI. Traditionally that meant reading a header, a specification and example code, then writing the glue yourself, which is days of work for someone new to it. That glue is exactly what a coding agent is good at. Each kit ships everything the agent needs to read:

  • The C header, the full interface, with every call and structure.
  • The specifications: for Reamer Research, how orders fill and what the result report contains; for Reamer Server, the configuration, the event bus and the strategy socket protocol.
  • Code in source: the supported Python package and C++ wrapper for Reamer Research; reference code for Reamer Server, a working server in Go with C, C++ and Rust starting points.

You describe what you want. The agent reads the kit and writes the wiring.

What the Reamer Server recording shows

The recording starts from a fresh copy of the kit, with no source code and no earlier exposure, and a wall clock in the frame. In about 19 minutes (watch), Claude Code wrote a trading server in C++ with its own FIX 4.4 broker connector and a gate with an instrument allowlist and a position limit. Against the kit's simulated venue it sent 6 orders: 5 filled, and the gate rejected 1 with its exact reason. It was recorded against version 4.2.1.

For Reamer Research, the product page shows the whole quickstart in Python and C++ and the visual trade diagnostics tool it opens. See How long does integration take?

What you still decide

An agent removes the learning curve of the interface, not of trading. These stay yours:

You should still read what the agent writes, as you would any code that trades your money.

Next questions

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.Which languages can I write strategies in?For Reamer Research, Python or C++: a pip-installable package and a one-header C++20 wrapper ship in the kit. Underneath is a stable C ABI, so any other language that can call C can wrap it, live trading included. For Reamer Server, the gate and the broker connector are written in C, C++, Rust or Go, and strategies connect over a socket from any language, Python included.Why use Reamer Labs if I want to build my own trading system?You still build your own system. Reamer Labs supplies only its core, the part that has to be right and works the same for everyone. Reamer Research is the research engine, with fill and cost rules already written and tested. Reamer Server is the order core, with order state, sequencing and a record of every decision. You build everything around them your own way, including strategies, data, risk rules, the broker connection, storage and monitoring.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.

Buy a licenceKey and kit by email on payment.