Get Started

Execution Wizard

Signals in.
Orders out — on your machine.

LLMCHARTS is software only. The Execution Wizard runs locally on your device or VPS, receives signals from the platform, and routes orders to your broker. Keys never touch our backend.

Download Wizard

How it works

Cloud signals.
Local execution.

The platform produces and delivers signals. Your wizard — running where you choose — authenticates, selects feeds, and places orders at the broker. We never hold API keys or submit orders from our servers.

Setup

Four steps
to a live route.

The wizard walks you through login, where orders leave from, which feeds to arm, and a live log so you can see every hop.

  1. 01

    Log in

    Sign in with your LLMCHARTS account so the wizard can receive signals addressed to you. Auth tokens stay on the local process.

  2. 02

    Choose location

    Pick where orders are routed from: this device, or a remote server you operate (or a third-party host you trust). LLMCHARTS does not run that hop for you.

  3. 03

    Select signal feeds

    Arm the feeds you want executed — your desk alerts, shared community signals, or strategy packs. Unselected feeds never leave the cloud as executable intents for this wizard.

  4. 04

    Monitor logs

    Watch receive → route → broker ack in one stream. When something fails, the failure stays on your machine — inspectable without opening a support ticket into our order path (we don’t have one).

Download

Install the wizard.
Keep the keys.

Placeholders for local review — binaries ship when the public build opens. Prefer a VPS for always-on routing; use this device for desk-side paper trading.

Local preview — download links are disabled until the first public build.

Principles

Software only.
You own the hop.

No cloud order path

LLMCHARTS does not submit orders to brokers. If the wizard is offline, nothing routes — by design.

Keys stay local

Broker API credentials live in the wizard process (or your secrets store on the VPS). Cloud never receives them.

Feeds are opt-in

Only armed signal feeds produce executable intents for your instance. Everything else is ignored.