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

Where does the market data come from?

From whichever vendor you choose, in one call. Reamer Research's bundled fetchers pull historical bars from your own Alpaca or Databento account straight into a backtest, and bars of any type from any other source go in as arrays or as memory-mapped files built from CSV. You pick the vendor, pay it directly and switch whenever you like, and the engine stays lean because it carries no data feed of its own. Reamer Server takes orders from your strategies, which price from your own feed.

From whichever vendor you choose, in one call. Reamer Research's bundled fetchers pull historical bars from your own Alpaca or Databento account straight into a backtest, and bars of any type from any other source go in as arrays or as memory-mapped files built from CSV. You pick the vendor, pay it directly and switch whenever you like, and the engine stays lean because it carries no data feed of its own. Reamer Server takes orders from your strategies, which price from your own feed.

The kit includes synthetic sample bars inside Evaluation Mode, so the quickstart runs on its first try.

Getting bars into Reamer Research

  • From Alpaca or Databento. python/fetchers/ downloads historical bars from your own Alpaca account (US stocks and crypto) or Databento account (OHLCV, including continuous futures) straight into a backtest, and examples/fetch_and_run.py does it in one command. Alpaca crypto needs no account. Alpaca stock bars arrive adjusted for splits and dividends. Each Databento request is priced first, and one over your limit is refused.
  • Arrays from any source. Load bars from CSV with pandas or numpy, a database or a vendor API, and pass them in as arrays: timestamp, open, high, low, close and volume for each bar. This works from Python, C++ or any language that can call C.
  • .bin files. bin/reamer-csv-build AAPL.csv AAPL.bin converts a CSV. It detects the delimiter, columns and timestamp format, and reports what it skipped. Timestamps are whole seconds, so two rows at the same timestamp stop it unless --keep-first keeps the first bar of each second. It needs no license. Pass .bin paths from Python or C++, or call reamer_run_backtest_files(), and the files are memory-mapped, so a dataset larger than RAM runs, and a start and end time select a date range without rewriting them.
  • One instrument per file. If a CSV holds several symbols, the converter stops until --symbol selects one.
  • Any bar type. Time, tick, volume, dollar, imbalance or your own custom rule. You build the bars, and the engine treats every type the same way. OHLCV is the record format, not a limit on how a bar was built.
  • Several instruments at once. Each instrument has its own series, and timestamps do not need to line up across them. Every instrument is cut to the range they all share, so the shortest series sets the run's length.
  • Non-price data, such as earnings dates or an index level, can be attached to each instrument from Python, C++ or the C interface. A bundled tool converts it from a two-column CSV.

What the engine expects from your data

  • Data quality. A bar with a NaN or infinite price stops the run with an error. Wrong prices, missing bars or bad prints do not; they produce wrong results.
  • Corporate actions. Unadjusted equity data gives wrong results with no warning.
  • Futures rolls. Supply a continuous series. If it is unadjusted, you can declare the roll months (roll_cycle_months in Python), and the engine stops treating the jump at each roll as a real price move.

See How do I backtest a strategy that uses earnings dates or other non-price data? and What is Reamer Research?

Next questions

Can Reamer Research backtest tick, volume or dollar bars?Yes. Reamer Research takes bars of any type: time, tick, volume, dollar, imbalance or your own custom rule. You build the bars and the engine treats every type the same way. Each bar's real trade count can drive its fills, and instruments sampled at different moments can share one portfolio.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.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.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.How fast is it?On a 64-core AMD EPYC 9575F and release 4.6.0, Reamer Research replays about 1.8 million bars a second in one backtest, and Reamer Server takes an order from a strategy to an accepted event in a median of 10.3 µs, with about 200,000 to 220,000 orders a second across many strategies. Each figure comes with the conditions it was measured under, and both kits include a benchmark to run on your own hardware.

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.