One maintainer, in writing
Reamer Labs is built and maintained by Chaitanya Palghadmal. Chaitanya started as a retail trader and became an independent quant researcher, with a computer engineering degree and a master’s in data analytics behind the data work. Reamer Labs is based in Pune, India. The person who writes the engine also publishes its benchmarks and answers its support email.
Why it exists
Reamer Labs began as a research hobby: self-taught quant methods applied to equity portfolios, sector ETF portfolios, currency pairs, and crypto perpetuals.
The tooling was the problem. Every study was its own Python script in its own sandbox, and small differences between them made results drift from one study to the next. The research loops were also too slow for strategies at any real scale.
So the goal became one engine for research and one for live execution, built to the same execution rules, fast enough that a single ordinary laptop could do the work of a trading desk’s infrastructure. Halfway through building it, it was clear other traders needed the same thing, and it became a business.
What that means for you
Answered by the author
Email support is included with every licence, not sold as an add-on. There is no front line to get past: questions go to the person who wrote the code. Covered hours are 09:00 to 18:00 IST (UTC+5:30), weekdays.
No sales process
Prices are on the pricing page, checkout is through Paddle, and the key and kit arrive by email on payment. A month of Reamer Research, or a 30-day Reamer Server trial, is how you find out whether it fits.
Nothing to trust with your code
Both products run on your infrastructure. Strategy code and order flow never leave it; licence activation is the only contact with Reamer Labs.
How the claims are backed
There are no customer quotes on this site. Instead of asking you to take anyone’s word, every figure links to the data behind it, and the integration claims are recorded end to end.
Three uncut recordings
Claude Code, given only the shipped kit documents with no prior exposure and no source access, integrates each product while a wall clock runs. One recording is on the home page, one each on Reamer Research and Reamer Server.
Method, written up in full
Predictable Trading Infrastructure on Many-Core CPUs: Latency, Concurrency, Determinism, and Repeatability on a Single-Socket AMD EPYC 9575F. The measurement method behind the latency, concurrency, and determinism figures on the product pages.
Every output, unedited
The raw benchmark artifacts: the console and CSV output behind every published figure. Where a raw file and a summary differ, the raw file is authoritative.
The results, written up
What the EPYC runs showed for Reamer Research and for Reamer Server, with their caveats stated plainly.
Four backtesting engines, measured
What a Backtest Costs runs Backtrader, NautilusTrader, LEAN and Reamer Research on the same data and strategies, with the outcomes that would count against Reamer Research stated in advance. The raw results and runners are on GitHub, and the blog post sums it up.
The whitepaper, measured again
Does the Operating Envelope Survive an Upgrade? repeats the whitepaper's measurements on release 4.6.0, a new kernel and a new compiler. All five findings held. The raw outputs are public, and the blog post sums it up.
If Reamer Labs stops
A single-maintainer vendor has a bus-factor question to answer. The answer is a source escrow you fund and control. It protects your deployment without handing over the source.
The full terms, including the release-control process, are in the kit under LICENSING.md. To set one up, write to [email protected].
Get in touch
Questions before buying: [email protected]. Licensed and need help: [email protected].