Finoways Algorithmic Trading Software: Scope and Limits
October 1, 2026
At Finoways, “algorithmic trading software” means software and research tools built to apply predefined trading logic to FOREX, COMEX and US markets. Depending on the tool and its configuration, that logic may help analyse market data, identify conditions, calculate risk parameters or automate parts of an order workflow.
It does not mean guaranteed profits, fixed returns, personalised investment advice or a managed trading account. Software can follow programmed instructions consistently, but it cannot know the future, eliminate losses or protect a trader from every market, technology or execution risk.
What algorithmic trading software actually means
An algorithm is a structured set of instructions. In trading, those instructions define what the software should do when particular market conditions occur.
A simplified rule might say:
If price moves above a defined level, volatility remains within a chosen range and the permitted trading session is open, generate a trade signal. Set the proposed position size using the account-risk limit and place or suggest a protective stop according to the configured rules.
Real trading logic may include more conditions, but the principle is the same. The software does not make intuitive judgments in the way a person does. It processes the available inputs and follows its programmed rules.
The exact scope varies by product, market, broker connection and configuration. Some tools may focus on analysis or signals. Others may support semi-automated workflows, where the trader approves an action. A fully automated setup may be able to send eligible instructions to a broker when all configured conditions are met. Traders should verify the functions of a particular service rather than assuming that every algorithmic product works in the same way. The current scope can be reviewed on the Finoways services page.
What the software may do in a trading workflow
Rule-based trading tools can support several stages of a trading process. Depending on the specific tool, these may include:
Market monitoring: checking prices or other defined data without requiring a trader to watch every movement manually. Condition detection: identifying when a programmed combination of technical or market conditions occurs. Signal generation: indicating that an entry, exit or adjustment rule has been triggered. Risk calculations: using inputs such as stop distance and maximum risk to estimate an appropriate position size. Order instructions: preparing or, where supported and authorised, transmitting an order instruction to the trader’s broker. Trade management: applying predefined rules for stops, targets, time-based exits or other adjustments. Record keeping: producing data that can help a trader review how a rule behaved.
These functions are tools rather than predictions. Detecting a valid setup only means that the programmed conditions were satisfied. It does not mean that the resulting trade must be profitable.
A hypothetical example of stop loss and lot size
Consider a hypothetical FOREX strategy with an account balance of $10,000. The trader sets a maximum intended risk of 1% for one trade, equal to $100.
The algorithm identifies an entry and calculates that the stop loss would be 50 pips away. If, for the relevant currency pair and account denomination, one standard lot has a hypothetical pip value of $10, then one standard lot would expose approximately $500 over a 50-pip stop distance. To target approximately $100 of risk, the calculated position size would be 0.20 lot.
The simplified calculation is:
Position size = permitted monetary risk divided by the monetary risk per lot at the selected stop distance.
If the trader changes the size from 0.20 lot to 0.40 lot while keeping the same stop distance, the intended exposure approximately doubles from $100 to $200. This demonstrates why lot size is not just an entry setting; it is a central part of risk control.
Actual results can differ from the calculation. A stop order does not guarantee an exit at the exact stop price. Fast markets, gaps, low liquidity, spread changes and slippage can produce a larger loss. Commissions, financing costs and currency conversion may also affect the final account result.
Risk controls help, but they are not guarantees
An algorithm can be programmed with controls intended to limit exposure. Common examples in rule-based trading include:
a maximum risk amount or percentage per position; a stop-loss rule; a cap on the number of simultaneous positions; restrictions on trading sessions or market hours; spread, volatility or liquidity filters; a daily loss threshold; rules that prevent additional entries after specified conditions occur.
These controls can make a process more disciplined. They may prevent an algorithm from deliberately taking a position that exceeds its configured limits under normal conditions. However, they cannot guarantee that realised losses will remain at the intended level.
For example, a market could reopen beyond a stop price, a broker could reject an order, or a connection could fail before an instruction is received. Risk settings should therefore be treated as safeguards within a broader risk-management process, not as insurance against loss.
What algorithmic trading software does not promise
No guaranteed or fixed returns
No trading algorithm can legitimately guarantee that every trade, month or market period will be profitable. Market behaviour changes, and a strategy that worked under one set of conditions may perform differently when volatility, liquidity, correlation or participant behaviour changes.
No guaranteed win rate
A high percentage of winning trades would not, by itself, prove that a system is profitable or suitable. A strategy could have many small gains and occasional large losses. Another could have fewer winning trades but larger average gains. Win rate must be considered alongside loss size, drawdown, trading costs and overall risk.
No elimination of drawdowns
Drawdown is a decline from a previous account peak. It can occur even when an algorithm operates exactly as designed. Consecutive losses, abnormal market conditions and execution differences can all deepen a drawdown.
Software may create an instruction at a particular price, but the broker and market determine whether and where it is filled. Latency, slippage, partial fills, rejected orders and spread expansion can cause live execution to differ from an algorithm’s theoretical result.
No assurance that historical results will continue
Backtests and historical analysis can help traders study how rules would have behaved using past data. They remain simulations and can be affected by data quality, unrealistic execution assumptions, overfitting and omitted costs. Strong historical output does not ensure similar future performance.