Introducing plutarc: Algorithmic Trading, Orchestrated
For those who know me, this will not come as a surprise. I have always been drawn to markets — not just the surface movement of price, but the structure beneath it. The way liquidity pools and dissipates. The way a level holds or doesn’t. The way what looks like noise, studied closely enough, starts to reveal something closer to a script. That fascination never really left me, and over time it became something more specific: a belief that the edge in markets, for the kind of participant I am, is not intuition or timing or courage. It is system. It is discipline applied so consistently that emotion simply has no room to interfere.
That belief is what eventually became plutarc by Valeon.
The project has taken a long time, and it has taken many forms. Different names, different assumptions, different scopes. Some versions were too ambitious for the moment. Others were technically sound but wrong in their foundations — built on ideas that looked reasonable until the market told me otherwise. Each version taught me something. Each one narrowed the question. What survived was not the first idea, or the second. It was what remained after the process of actually testing things — weeks of backtesting, paper trading, testnet runs, live deployment, a full code audit — had stripped away everything that did not hold.
Part of what made it take as long as it did was a choice I made early and never walked back: to build the bot architecture from the foundation. No external trading libraries. No CCXT, no abstraction layers someone else designed for someone else’s assumptions. My stubbornness on that point cost time — more than I will admit — but it also meant that every layer of the system is one I understand completely, one I can reason about, one I can trust when it matters. There is a certain kind of confidence that only comes from having built the thing yourself, and I was not willing to trade that away for convenience.
plutarc is a platform for orchestrating the deployment of trading bots. Strategies are configurable and composable — available as templates that you select, adjust, and deploy. A single user can run many bots simultaneously, each with its own configuration, each operating independently. At launch, it connects to BitMEX. It is not a system you hand your capital to and hope for the best. It is infrastructure you operate — one that gives you genuine control over how and where your strategies run. Bybit support is already in the works, with Binance to follow soon after.
The underlying philosophy has not changed from what I have always believed about markets: the goal is not frequency, it is asymmetry. Structured to lose small. Built to win when it matters. plutarc does not change that calculus — it gives you the environment to execute it properly, at scale, without the operational friction that usually gets in the way.
What that looks like in practice: five default templates drawn from my own personal trading, included not as finished strategies to copy blindly, but as reference points — concrete examples of how the system can be assembled, and a starting place for building something of your own. Behind them, 28 composable strategy components with every parameter configurable, nothing locked away. Before any of it goes live, a backtesting suite lets you test against historical data so that you are not discovering the weaknesses of a strategy at the worst possible moment. Once you are running, plutarc records analytics on every trade — not just the outcome, but the signals that fired entry and exit, and MFE versus MAE breakdowns to help you understand where a strategy is leaving money on the table or carrying unnecessary risk. Five types of exit guards give you precise control over how and when a position closes. The tools are there to refine, not just to run. To learn more I would recommend taking a dive into the comprehensive documentation on the site.
The orchestration layer is something I am particularly proud of. Each bot instance is provisioned through a custom system built specifically for plutarc. Dedicated compute, no shared execution environment, no resource overlap between instances or users. When you deploy through plutarc, the infrastructure matches the seriousness of what you are doing with it.
It is available now as a subscription, starting at £48 a month. This is not a signals service. It is not copy-trading. It is a platform for people who want to run their own edge, on their own terms, across as many bots as their strategy demands.
Some projects are built because the market opportunity is obvious. Others are built because you kept noticing a problem you could not stop wanting to solve. plutarc belongs to the second category — and more than most things I have built, it has had to earn its existence. I am glad, finally, to be able to say it has.
