Roadmap
The desktop milestone, then the work in progress and the work that comes next; dated changes are on the Version page. Each item ahead carries a status and no date.
The desktop milestone, feature by feature
Each line above is described in the documentation, with the method and limits behind its figure. The counts come from the catalogue inside the desktop build, measured on 2026-09-16.
Open full size
Open full sizeEvery surface reports the same version
The desktop app, installer and agent interface carry one release number. An automated release check compares their major, minor and patch values before packaging. Pre-release suffixes remain descriptive: 0.1.0 and 0.1.0-alpha name the same milestone.
What a later entry is allowed to claim
An entry names what changed and the evidence behind it: an executable validation for a node or the measurement behind a figure. Without that evidence, it remains an intention.
Published counts are read from the catalogue shipped with the desktop build, so they remain tied to the release they describe.
Install the current desktop software
The Windows installer and the macOS .dmg are in your account, with their install steps.
In progress, then next
In progress means the work has started; Next means we have scoped it and start it after the items in progress. Version 0.2.4 runs none of these items, and none carries a date: a date we have not measured would read as a promise. The community fund described below comes after the desk and has no status yet.
Turn a running bot's log into a backtest session
A bot that trades produces a log. Today that log and the research graph that produced the strategy live apart, so a live result cannot be replayed against the assumptions it was built on.
The direction is a reader that rebuilds a session from the log, so the executed fills and the modelled ones sit in the same run and can be compared bar by bar.
The interface sketches this direction today. No bot-log reader is available; the product reads its application log.
Measure a live bot with the metrics used in research
Trial counts, deflation against the search and drawdown under a regime are the figures a reviewer asks a backtest for. They stop at the edge of the desktop.
The direction is to compute the same figures on a live track record, so a bot is read with the instrument that judged it before it was deployed.
The proposed scope covers a bridge from the node graph to orders, a kill switch, paper trading first, and a separate workspace for live state. None of it is available today. Direct broker execution is planned once the applicable financial regulation is in place; until then, a validated strategy is exported and runs on the platform of your broker.
A place to publish a strategy with its evidence attached
A published strategy is usually a curve and a claim. What a reader needs is the run that produced it: the graph, the costs declared, the multiplicity correction applied.
The direction is a listing where the paper travels with the strategy, under one set of publication requirements fixed in advance and applied to the whole catalogue.
This is the one direction with something visible in the build. The extensions screen carries a Community marketplace entry tagged Soon, with no action wired to it. It is explicitly marked under development and exposes no action.
Capital allocated against published evidence
The direction is a fund that allocates to strategies from the market above, on the evidence each one carries.
Two eligibility thresholds are already settled and written down: eight years of data and six months of live track record before a strategy is admissible. The structure, the terms and the rest of the evidence bar remain open. Managing capital for third parties is planned once the applicable financial regulation is in place.
The order of work is the desk first, then the fund. The fund depends on evidence produced by a desk that people can use.
What a roadmap line is worth here
A direction above is scoped work, and scoped work carries no commitment. What separates these entries from the product is evidence of availability: a product claim describes behaviour a visitor can use, while a direction describes intended scope.
The version history states what the current milestone contains, feature by feature.
Creator payouts in more countries
The affiliate program pays creators in 34 countries today: the European Economic Area, Switzerland, the United Kingdom, the United States and Canada, the regions where Stripe sends our payouts. The full list is on the affiliate page.
The direction is to open other countries with payouts that run on their own each month, as they do today. No date is attached, and until then creators elsewhere cannot join.