Lucrum Superius Systems

For quants

Most of the work in a quantitative workflow is not the idea. It is the capture pipeline, the order lifecycle, the reconciliation, and the long argument with yourself about whether a result is real. This is that scaffolding, already built and already hardened against the specific ways each part fails in production.

It supplies no edge, and this page makes no claim about what any strategy earns. What it offers is that the measurement is trustworthy and the execution is boring — which is the part that usually costs a team months.

What it costs to run

One small virtual machine. The whole stack — order book, detector suite, scoring, risk, execution and the web terminal — was built and measured on a 2-vCPU instance with 945 MiB of RAM. One instrument runs comfortably there; three or four is the measured ceiling rather than a guess.

Licensing is a flat subscription, not a share of anything you make, and not a per-seat charge. See plans.

Quantitative researchers

The expensive part of research is not running a regression. It is obtaining data you can trust and then not fooling yourself with it.

The part that is hardest to buy is the catalogue of ways this measurement goes wrong, written down with the wrong answer each one produced. Pooling windows with different base rates once reversed a result's sign at high confidence. Counting an unchanged price as a directional win manufactured an effect out of nothing — the mid is unchanged on 86.8% of one-second intervals on a venue quantised at a cent. A rotated log file truncated history and flipped the sign of an answer. A frozen capture read as a quiet market until liveness was judged on top-of-book quantities rather than price, because a price can legitimately sit still and sizes cannot.

Quantitative developers

Sending an order is a morning's work. Everything after it is the year. This is the part that only appears once real money is moving.

Interfaces are declared per module and the mocks in the test suite are typed against those declarations, so a changed signature fails at the boundary. Around 1,278 tests, and the tests are themselves mutation-checked: a test that cannot fail when the behaviour it describes breaks is treated as a defect rather than as coverage.

Quantitative traders

After the fact, the only question is what actually happened. Most journals cannot answer it because they record the plan and not the outcome.

The terminal that shows all of this runs as a separate process that imports nothing from the trading stack and reads a published snapshot. It therefore holds no exchange credentials, has no code path that can place an order, and keeps serving last-known state while the runner is down.

What you still have to bring

Worth saying plainly, because the opposite is what most infrastructure pitches imply.

If that division of labour is the one you want, request access and we will send the agreement, the system requirements and an invoice.

Important information

Trading leveraged derivatives carries a substantial risk of loss and is not suitable for everyone. This page is not financial advice, nor an offer, a solicitation or a recommendation to buy or sell any instrument, nor a recommendation of any trading strategy. No performance claim is made anywhere on this site, and no past or projected result should be inferred from any description of the software.

We provide software and infrastructure. We do not manage client money, take custody of client assets, or exercise discretion over client accounts. Any prospective arrangement is subject to written agreement and to the licensing and suitability requirements of the relevant jurisdiction.