Get Vike Trader, and run it

Three ways to run it

One engine underneath all three. A strategy you backtest in the desktop app is the same strategy the daemon runs unattended, and the same one your agent drives through the CLI.

Every file the release publishes is listed further down, with what each one is.

Neither install path updates itself

Stated plainly rather than left to be found on the second release. cargo binstall records the install under a crate version that never moves, so re-installing needs --force. And scoop update cannot advance this bucket at all: the public mirror is re-created as a single orphan commit on every publish, and scoop refreshes a bucket with a plain git pull, which refuses an unrelated history. A later release is installed by removing the bucket and adding it again.

# cargo-binstall — re-install over the old one
cargo binstall --force --git https://github.com/vike-io/vike-trader vike-cli

# scoop — remove the bucket, add it back, then update
scoop bucket rm vike
scoop bucket add vike https://github.com/vike-io/vike-trader
scoop update vike-cli

The desktop app and the daemon have no such quirk: a desktop release is a new binary you download, and the image is a new docker pull. When the bucket moves to a repository of its own, scoop update alone becomes the whole update and this section loses its second half.

Run it in five minutes

No account, no email, no trial. Download it and it runs — and everything mounts paper until your policy file says otherwise, so the first run is safe by construction.

# then verify what you downloaded, from the same directory
sha256sum -c SHA256SUMS --ignore-missing

# one project folder holds settings, state and data
R=$HOME/vike-trader
mkdir -p "$R/settings/state" "$R/data"
docker run --rm vikeio/vike-tradehub --template > "$R/settings/tradehub.toml"

# edit the profile (venue, symbol, strategy), then:
docker run -d --name vike-tradehub   --user "$(id -u):$(id -g)" -v "$R":/project   --restart on-failure --stop-timeout 10   vikeio/vike-tradehub

// Claude Desktop / Claude Code — add to your MCP config
{ "mcpServers": {
    "vike-trader": { "command": "vike-cli", "args": ["mcp"] }
} }

Every file the release publishes

Direct downloads, always the newest release under each name — nothing on this page pins a version.

Verify what you downloaded

Every release ships SHA256SUMS beside the binaries, and each binary carries an embedded SBOM (cargo-auditable) you can scan against RustSec without trusting us about its dependencies.

• SHA256SUMSpublished beside every binary in the same release
• Embedded SBOMcargo-auditable writes the dependency list into the binary itself
• RustSec scannedthe shipped artifact is scanned against the advisory database

sha256sum -c SHA256SUMS --ignore-missing

Download SHA256SUMS · All assets and release notes on GitHub

Build it yourself

The source is published at github.com/vike-io/vike-trader — source-available under FSL-1.1, and every release becomes Apache-2.0 two years on. A default build needs no native dependencies.

cargo build --workspace