Reamer is a trading experimentation environment. That's a specific, deliberate choice of words, not a stylistic preference — the more obvious labels were each considered and rejected for concrete reasons.
Not "backtesting framework"
Backtesting is real and central to what Reamer does — a strategy meets historical data, orders get filled, a result comes out. But that's one stage of a longer process, not the whole of it. Calling the whole product a "backtesting framework" names the middle step and leaves out everything on either side of it: forming the idea in the first place, inspecting exactly what happened after the run, deciding whether the result would survive data it hasn't seen, and carrying whatever was learned into the next idea.
A single backtest, in isolation, proves very little — a strategy can look excellent on one run and be indistinguishable from noise. Naming the category after that one stage makes it sound like the point is the run itself. It isn't. The point is what happens before and after it.
Not "research environment," on its own
"Research environment" is closer, but it describes a place, not a discipline. A folder of notebooks, a spreadsheet, and a shared drive is also, technically, a research environment — it doesn't commit to anything about how rigorous the research inside it has to be. It doesn't distinguish evidence-based testing, where a result has to survive realistic costs and a robustness check before it's trusted, from open-ended tinkering, where a good-looking number is treated as the end of the story.
The word that was missing is the discipline itself, not just the setting it happens in.
Not "research operating platform"
This one overreaches in the other direction. "Platform" and "operating" both imply infrastructure ambitions — hosting, orchestration, running things on someone's behalf, multi-tenant scale — that go well beyond what the actual loop needs. Reamer runs locally, on one machine, with no server in the middle. Naming the category after infrastructure it doesn't have and isn't trying to build would promise something the product was never going to be.
What "experimentation environment" actually names
The category needed to name the loop itself — idea, implementation, execution, inspection, validation, iteration — rather than any single stage of it, and it needed to commit to evidence as the operating discipline instead of leaving that implicit. "Experimentation environment" does both: it's a place (environment) built around a specific, repeatable method (experimentation), not a generic research space and not a single pipeline stage wearing the whole product's name.
"Systematic trading laboratory" is decent secondary vocabulary for the same idea, and shows up in narrative writing for exactly that reason — it ties naturally to determinism and controlled, repeatable conditions. But "laboratory" also connotes a slowness and formality that doesn't match the actual experience of using Reamer, which is closer to an idea expressed in thirty lines and tested in seconds than to anything resembling lab-coat process. Useful in reserve. Not the primary name.
Why this is worth being precise about
A category name is a promise about what to expect. Call something a backtesting framework and someone reasonably expects a tool for running backtests, not a way to reason about whether an idea deserves capital behind it. Call it a research operating platform and someone reasonably expects infrastructure that isn't there. "Experimentation environment" is the name that's supposed to still describe Reamer accurately a decade from now, because it describes the loop — and the loop is the part of this product least likely to change.
Full reference: docs · The execution model behind the "test" part of the loop: execution specification · The workflow this maps onto: reamerlabs.com