RezSync Algo documentation

RezSync Algo is a downloadable AI-assisted trading application for cTrader. It connects broker account context, market sessions, symbol constraints, risk settings, economic events, and an AI decision layer. It can produce review-only signals, send demo broker orders, or, only after explicit setup, send live broker orders.

The product is not a hard-coded guaranteed-profit strategy. The useful edge it tries to protect is disciplined decision quality: trade only when context, risk/reward, confidence, market state, and account limits line up. A skipped trade is often the correct output.

1. 1Download RezSync Algo from the Algo product page.
2. 2Launch the app and complete the setup hub.
3. 3Connect a cTrader demo account before considering live mode.
4. 4Choose Managed RezSyncIQ or bring your own model provider.
5. 5Select symbols from the broker-backed symbol list and verify them.
6. 6Keep execution in Review only or Demo broker orders until you understand the logs.

The Setup hub is the onboarding source of truth. Do not skip items because each one removes a different class of failure: account authorization, broker authorization, symbol mismatch, missing subscription, missing AI provider, or unclear risk.

Quick Setup creates or edits the trading profile. Keep it boring and explicit: the profile name should tell you whether it is demo or live, and symbols should come from the broker picker whenever possible.

RezSync Algo is built around cTrader. The first setup path connects a cTrader account through the RezSync-managed OAuth flow or direct broker credentials where supported. The connected environment matters: demo accounts can place demo orders; live accounts are treated separately and require live confirmation.

RezSync Algo separates the trading engine from the AI hosting path. BYOM users configure their own AI provider, API key, model, base URL, and JSON behavior. Managed RezSyncIQ users use a RezSync-hosted decision path with usage controlled by their subscription.

Execution mode decides what happens after the AI produces a valid decision. It does not change market risk, symbol availability, or the need to verify broker setup.

Advanced Settings is where the serious controls live. BYOM users see AI provider fields. Managed RezSyncIQ users do not need provider keys, but still use this screen for execution, risk, schedule, sessions, and notifications.

Risk settings are not cosmetic. They define how much room the engine has to act after the AI decision is produced.

RezSync Algo should be risk-first, not lot-first. The AI can propose the trade idea and the technical levels, but the final executable size is calculated by the engine from the selected risk profile, real account state, stop distance, and broker symbol metadata.

The selected timezone controls the local days you allow the bot to open new trades. Internally, the app converts current UTC time into your selected timezone, then checks your selected local day. The saved hour window is 0 to 23, meaning the full selected local day.

Market sessions, broker rollovers, symbol market open/close, and economic-event timing stay automatic and UTC/DST-aware. This avoids shifting real market clocks just because the user lives in a different timezone.

Notifications are for awareness, not proof that a trade was safe. Use them to notice signals, fills, closes, and guardrail errors, then check logs or the dashboard for the full context.

Email is deliberately lean and event-driven, so it stays useful instead of becoming noise: the algo starting and stopping (with a session summary), each trade opened and closed (with its outcome), and critical algo-only alerts such as a lost connection. It does not email a periodic digest, and it does not duplicate account-status alerts — margin, drawdown, and stop-out emails are sent by your broker, so the app stays out of the way rather than sending the same warning twice.

Broker symbol verification checks that configured symbols exist on the connected cTrader account and can be sized safely. This matters because the same common symbol, such as XAUUSD or EURUSD, can be exposed differently by different brokers or account types.

1. Open Quick Setup.
2. Pick symbols from the broker-backed symbol list, not memory.
3. Save the setup.
4. Run Verify broker symbols.
5. If any symbol is blocked, remove it or pick the broker-supported version.

The dashboard is the operating surface. It shows environment, account state, setup readiness, recent decisions, positions, broker connectivity, and logs. Treat warning states as real blockers, especially around broker connection, subscription, symbol verification, and execution mode.

Win rate is not the edge by itself. RezSync Algo is designed around expectancy-aware decision quality: risk only matters when the potential reward, confidence, invalidation, symbol conditions, and account limits make sense together.

Backtesting is limited when AI uses current available information, broker state, live spread, current news, and runtime context. The most honest evaluation path is structured forward testing: run in Review only, then demo orders, then inspect decision logs before considering live execution.

News and economic calendar data are normalized to UTC for timing. The AI may receive compact context about upcoming events, high-impact windows, and recent market sentiment, but the engine should not invent news or trade if the data needed for a decision is missing.

Logs are how you audit the system. They are also what support needs when something feels wrong. Do not rely only on what you remember seeing in the terminal.

{
  "symbol": "EURUSD",
  "action": "hold",
  "confidence": 0.61,
  "execution_blocked": true,
  "reasoning": "Risk/reward and session context did not meet threshold"
}

Runtime Settings are smaller operational preferences, not the trading model itself. Use them to control dashboard refresh cadence and what the terminal log view emphasizes while the engine runs.

RezSync Algo can keep the trading engine running after the dashboard is closed, but it should never feel hidden. Every background path uses the same headless bot mode as the dashboard, writes status to disk, and can be stopped by the operator.

rezsync background start
rezsync background status
rezsync background stop
rezsync background paths

RezSync stores generated trading evidence locally so a restart does not erase context. Broker open positions and pending orders still come from cTrader, but market theses, profit-manager decisions, lifecycle events, schedules, and logs can be retained on the machine.

Profit management exists to defend open trades after entry. It should not use one hard-coded pip threshold across every market. EURUSD, XAUUSD, indices, and crypto do not share the same tick value, volatility, or broker contract terms.

RezSync Algo checks the RezSync update manifest for the current platform. When a newer version exists, the update screen shows the current version, latest version, release name, release notes, install safety status, and download action. When automatic download is enabled, the header can show downloading or ready state before the user opens the update screen.

The written docs are the canonical source. Videos should be short walkthroughs that point back to these anchors, use demo accounts only, hide account IDs and device codes, and avoid profit claims.

Live mode is intentionally slower to enable. A user should first confirm that setup is complete, symbols verify, demo execution behaves as expected, logs are understood, and risk settings match the account size and tolerance.

When contacting support, include the product, operating system, account environment, execution mode, symbol, timezone, recent log excerpt, and what you expected to happen. For broker issues, mention whether you changed accounts or symbols recently.