QOVARYX.
Downloads paused

The previous build was out of date, so we took it down rather than leave it up. Join the release list →

Ch. 01 — Release notes

Every build, and what changed in it.

This is the record of what shipped and when. It is written for someone deciding whether to trust the thing — so it includes the corrections, not only the additions. No build on this page is currently available to download.

The Qovaryx dashboard: account state, open positions and current signals, running locally on a Windows desktop
Qovaryx 3.0 — dashboard runs entirely on your machine

Ch. 02 — Current state

Where things stand right now.

Downloads are paused. The most recent build listed below is out of date, so it has been taken down rather than left up for someone to install. There is no release date — the next build ships when it has been through evaluation, and not before.

We publish no performance figures. Any return, win rate or accuracy number attributed to Qovaryx did not come from us. Nothing on this page states one, including the entries describing changes to how the software is evaluated.

Release news lands in the Discord first, and the reasoning behind each change ends up on the build log.

Ch. 03 — The log

What shipped, newest first.

Written in plain language. Where a release corrected something we had previously said, that is stated in the entry rather than quietly dropped.

3.0.2 2026-07-21
Fixed

Event-driven candidates no longer crowded out. The queue now considers time-sensitive, event-driven candidates before the ordinary per-cycle cap applies, instead of the cap potentially pushing them out.

Changed

Safer default on first run. When no configuration has been saved yet, the app starts in its conservative default rather than whatever was last used. Choosing between simulated and live account mode stays an explicit human decision.

Added

Windows startup toggle. The app can start with Windows; the setting is on by default and can be turned off.

Added

System tray. A tray menu opens the app and starts or stops the engine without changing the selected account mode. Closing the window keeps the app resident in the tray; Quit fully exits it.

Changed

Branding. The application window and tray icons use the Qovaryx artwork.

3.0.1 2026-07-21
Correction

The evaluation harness was wrong, so we fixed it and retracted what it produced. Exit handling and real-world trading friction were not being accounted for correctly. Every figure produced by the earlier version of that harness is withdrawn and none of it appears anywhere on this site.

Changed

Risk profiles re-anchored. All profiles were re-derived against the corrected harness, including realistic execution friction. Sizing is bounded by the profile you choose, and the shared safety layer stays active in all of them.

Added

An extra confirmation step before entry. Certain entries now require a second, independent confirmation before they are considered eligible. It rejects more than it admits, which is the point.

Changed

Several configurations demoted to observation-only. Three configurations stopped meeting the standard under the corrected harness and were moved to run without acting, so their behaviour can keep being measured.

Changed

Symbol groupings revised, and a probation group added. Symbols are grouped by how well the data supports evaluating them; a probation group holds names that are being watched before they are treated as ordinary.

Fixed

Risk-card wording. Several risk descriptions in the app overstated what the software does. They were rewritten to say what is actually true.

3.0 2026-07-20
Added

Four risk profiles. Conservative, Standard, Aggressive and Extreme change position and concurrency limits. The two higher profiles require an explicit acknowledgement, and none of them can switch off the shared safety layer.

Changed

One dispatch and risk layer for every configuration. All the strategy configurations now share a single path that checks what the connected broker can actually do before anything is constructed.

Added

Bring-your-own AI chat. Connect a hosted provider or a fully local model for analysis and chat. Provider credentials go in the operating system's protected store, and requests go only to the provider you picked. The chat surface cannot place an order.

Added

Circuit breakers that apply to every profile. Daily-loss halts, concentration limits, drawdown acknowledgement, fill-quality monitoring and realistic execution costs stay on regardless of which profile you pick.

Added

Explicit authority for every model. Each component is declared as acting, observing, providing context, or research-only. A component cannot influence an order unless it has been granted that role in writing.

Added

Refusal checks wired end to end. Scheduled-event blackouts, disagreement checks, and a hard refusal path can all return "no action". A missing or contradictory input is not converted into a guess.

Changed

Release hardening. A bundled runtime, strict resolution of packaged files, clean per-user data locations and manifest verification replace the fallbacks that only ever worked on a development machine.

2.5.4 2026-06-08
Fixed

The broker selector showed the wrong name. A status overlay was writing its text into the broker list, so the first entry displayed a data-source label instead of the broker's name.

Fixed

Broker choice did not persist. The settings panel was posting to an endpoint that did not exist and failing silently. Switching brokers now sticks across restarts.

Fixed

The connection light lied. It now reports green only when the broker actually returns data, amber when the connection responds but is empty, and red on error — instead of showing green for a broker that was never connected.

Fixed

Window and taskbar icon. The application identity is now set before the window is created, so Windows shows the brand mark in the taskbar, on pinned shortcuts and in Alt-Tab.

2.5.4 — early 2026-06-06
Added

The full specialist set shipped in the public build. Every specialist model is trained from scratch rather than adapted from a borrowed foundation model, and all of them run on the local CPU.

Added

A refusal layer over the combined result. Specialists are combined rather than trusted individually, and the refusal layer can demote a setup to "no action" before anything is submitted.

Changed

Advisory components stay advisory. Components not cleared to act remain observation-only unless deliberately enabled.

Fixed

Update check reported the wrong state. The app now distinguishes a development workspace from an installed copy instead of returning a generic failure.

Want the next entry as it happens? Release news lands in the Discord before it lands here, and the arguments behind each change end up on the channel.

Join the Discord

Ch. 04 — What happens next

No date. A standard instead.

The next build ships when it has been through the evaluation described on the home page, and not before. We would rather be late than ship a trading tool we cannot defend. Join the list and you will hear when it is ready.