Automated strategies

Koneth automated strategies use the Koneth Script (KAS) runtime. A strategy can react to bars, ticks, and position events and can place orders only after automated trading is explicitly enabled.

Desktop and cloud execution

Where it runs	Behaviour
Desktop Terminal (macOS and Windows)	Runs locally in the terminal and stops processing market events when that terminal runtime is no longer active.
Mobile-managed cloud KAS (iOS and Android)	Runs in the KAS environment owned by the selected trading server, even when the phone is closed.

Cloud KAS is server-local. It is not one central service shared by every broker. Each trading server stores and executes only the strategies belonging to its own accounts.

An organization enables cloud KAS once in Console settings. The same entitlement applies to every server owned by that organization, including Demo and real-money servers. Each strategy still has to be started explicitly and remains subject to the server’s account, market and risk checks.

Risk controls

Each strategy starts with server-enforced defaults:

• 1 lot maximum order volume.
• 5 maximum open positions and pending orders.
• 15 new orders per minute.
• 2% maximum daily loss against starting equity.

Edit these values under Risk controls while the strategy is stopped. The server checks every new order independently of the script. Closing and reducing risk remain available after a limit is reached.

Storage and runtime cost

Identical strategy source is stored once per trading server. Additional accounts using the same source reference the same stored version and retain only their own inputs and risk settings.

Starting the same strategy on several accounts still creates several independent cloud runs. Each run has its own isolated process, market subscription, risk state and audit log, so execution resources scale per active account. Stopped bindings do not consume a runner process.

Note

The organization must enable KAS in Console settings, and the selected trading server must have its KAS runner available. If the runner is unavailable, a requested run remains stopped.

Manage strategies from mobile

Open Settings → Automated Strategies while signed in to a trading account. The screen supports:

• Creating a KAS in the script editor.
• Importing or exporting a .ks file.
• Reviewing script-declared inputs before starting.
• Starting and stopping cloud execution.
• Reading runtime logs.
• Editing or deleting a stopped strategy.
• Setting order volume, exposure, order-rate and daily-loss limits.

Read-only investor sessions can inspect the strategy list but cannot create, edit, start, stop, or delete strategies.

Start a strategy

1. Review the script

   Confirm the strategy name, permissions, symbol, timeframe, inputs and automated-trading choice.

2. Enable automated trading

   A KAS cannot send a trade intent unless both the script requests the trading permission and the strategy has automated trading enabled.

3. Wait for the server runner

   The mobile screen changes from Starting to Running in cloud after the local runner claims the run and establishes its server session.

Only one cloud run of a strategy can be active. Starting a replacement run increments its server generation and makes older runner sessions invalid.

Stop safely

Stopping a KAS stops future signals immediately and revokes its cloud session. It does not close positions that are already open. Review those positions manually or let the strategy’s own stop logic manage them before you stop it.

Starting, editing, deleting, or enabling automated trading does not guarantee profit and does not replace the broker’s margin, market-session or risk controls.