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

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.

You still build your own system. Reamer Labs supplies only its core: the part that has to be right, works the same for everyone, and makes no one money by being written again. You build everything around it, your own way, in your own language and on your own machine.

That sits between the two usual choices. Building everything means months spent on plumbing before any strategy is tested. Buying a finished platform means taking its data, its brokers, its risk rules and its way of working. A core leaves the parts that are yours in your hands.

What Reamer Labs supplies

Reamer Research, the research core. A backtesting engine you use from Python or C++, built on a stable C ABI that any other language can wrap:

  • Fill and cost rules, written down in an execution specification that ships with the kit, with the engine tested against it. They cover market, limit and stop orders, gaps, stops and targets in the same bar, bid and ask, spread, slippage, commission, margin, overnight swap and futures rolls.
  • Byte-identical output for a fixed rng_seed, so a change in results is always your change.
  • About 1.8 million bars a second per backtest on release 4.6.0, fast enough to sweep.
  • 31 summary metrics plus every order, fill and trade, in a versioned JSON report.
  • Full position state and every resting order on each bar, with actions that re-price an order, move a position's stop and target, close all or cancel all.
  • A relay, reamer_relay_*, that sends the strategy's orders to your broker through the open-source receiver over the published protocol, and reads the fills back.

Reamer Server, the order-management core. An order management engine delivered as a library you link into your own program:

  • Order state and sequencing: eight order states, no overfills, and duplicate fills rejected.
  • A call to your pre-trade gate for every new order, cancel and replace.
  • Account state read from your broker connection, so there is no second ledger to drift.
  • Every decision published on an event stream, with Prometheus metrics and a health check.

What you build

  • With Reamer Research: your strategies, in Python, C++ or any language that can call C. Your data pipeline and your sweep, analysis and reporting scripts.
  • With Reamer Server: the gate's rules, which are your risk policy. The connector to your broker, plus your strategy processes, storage for the event stream, and dashboards and alerts.

Each product comes with working starting points: Python and C++ example strategies and templates for Reamer Research, and for Reamer Server an accept-all gate and paper broker in C++ and Rust, plus a full FIX 4.4 integration in Go. With the Python package or the C++ header, a first Reamer Research run takes a couple of minutes; on an uncut recording, a working Reamer Server integration took about 19. See How long does integration take?

Why the line sits there

The core is where a subtle bug costs money without anyone noticing: a stop filled at the wrong price, a fill counted twice, an order changed after it finished. It is also identical from one trader to the next, so writing it yourself adds nothing. The parts outside it are where traders differ: what you trade, how you size, what you will and will not risk, and which broker you use. Those stay yours.

When a core is not the right fit

  • The core itself is your edge, for example a fill or microstructure model better than anyone else's.
  • Your strategy lives in the order book or in options pricing, where specialist tools such as NautilusTrader or QuantConnect are built for that work.
  • You want everything done for you, including data, brokers and hosting. A full platform fits better.

Price

Reamer Research costs $20 per seat per month, cancel any time. Reamer Server costs $24,000 per seat per year, paid once with no automatic renewal. The Reamer Server 30-day trial costs $2,000. See pricing.

Next questions

What is Reamer Research?Reamer Research is a deterministic backtesting and live trading engine for Python and C++, with a visual trade diagnostics tool; its relay sends live orders to your broker. You install it with pip or include one C++ header, on your own machine. It is built on a stable C ABI, so any other language that can call C can wrap it, live trading included. It tests a strategy, diagnoses it trade by trade, sweeps it, reports it, and sends its orders live, to your broker through the open-source receiver over the published protocol. Every order fills tick by tick on a seeded tick path the engine generates inside each bar, from bar data alone. Its visual trade diagnostics tool charts every closed trade on its own bars beside every value your strategy printed. The same data, settings and seed give byte-identical results every run. It costs $20 per seat per month, cancel any time.What is Reamer Server?Reamer Server is an institutional order-management core that you build your own trading system around, delivered as a library with a stable C interface. It holds order state, puts every strategy's orders into one strict sequence, runs your own pre-trade rules on every order and records every decision with its reason. On a 64-core AMD EPYC 9575F with release 4.6.0 it took 60 ns per order across its interface and peaked at 220,446 orders a second, with latency steady up to one strategy per CPU core. Your venues connect through connectors you own, in C, C++, Rust or Go, starting from the kit's worked FIX 4.4 integration. It costs $24,000 per seat per year, with a $2,000 30-day trial.Is there a self-hosted order management engine I can build my own OMS around?Yes. Look for an engine you link into your own program, which keeps order state, puts every strategy's orders into one sequence and publishes every decision, while your pre-trade rules, broker connection and storage stay under your control. Reamer Server is built that way: an institutional order-management core for Linux that runs one strategy per CPU core with steady latency. It costs $24,000 per seat per year, with a $2,000 30-day trial.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.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.

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.