We develop custom prop trading automation software for traders managing funded, evaluation, and personal accounts — including multi-account execution, trade copying, automated strategies, and account-specific risk controls.
Nordman Algorithms develops custom prop trading automation software for traders managing funded, evaluation, and personal accounts. Projects can combine multi-account execution, trade copying, automated strategy or signal execution, account-specific risk controls, and platform, broker, webhook, or API integrations.
Automation can start from a manual trade, master account, strategy, indicator, TradingView alert, webhook, or API instruction. We translate that workflow into the required validation, risk, sizing, routing, execution, and monitoring logic, with the architecture selected around your accounts, platforms, brokers, verified prop-firm rules, and available APIs or data sources.
We design each project as one connected workflow: where the trading instruction comes from, what logic is applied before execution, and which accounts receive the approved action. We can automate a single stage or combine all three.
Automation can begin from the way you already trade. Keep the decision manual, use a master account, run a native automated strategy, trigger logic from an indicator, or send TradingView, webhook, or API instructions into the workflow.
Before an instruction reaches an account, the software validates the signal and account state, applies execution filters, calculates account-specific sizing, and checks the risk rules defined for that account. For funded and evaluation accounts, this layer enforces the rules verified for the project before the order is placed.
Approved instructions can be executed on one or many owned funded, evaluation, or personal accounts. Each account can use its own sizing, mapping, routing, and supported synchronization rules instead of inheriting one global setup.
Available capabilities depend on the target platforms, broker or prop-firm environment, available APIs and data sources, and the agreed project scope.
We build risk controls that apply account-specific limits before and during execution, instead of relying on one global risk profile.
The risk layer can combine drawdown and daily-loss controls, position limits, session and news restrictions, account lockouts, and monitoring around the rules defined for the target accounts.
Controls are configured from the rules verified for the project. Traders remain responsible for confirming whether automated trading, EAs, trade copying, and third-party integrations are permitted. We do not guarantee challenge outcomes or build systems intended to bypass account, identity, or risk controls.
Built for traders using prop, funded, and evaluation accounts — not for operators building prop-firm back-office infrastructure.
For traders managing owned funded, evaluation, and personal accounts through a repeatable automation workflow.
For traders who want software to apply defined evaluation or funded-account limits without implying a guaranteed challenge outcome.
We clarify the scope, architecture, price, and timeline before development begins.
Send your workflow, account types, platforms or brokers, prop-firm environment, risk limits, and any reference software you already use.
The final package depends on the agreed architecture and target environment.
We build around the trading platform, broker connection, and account environment your workflow actually uses.
Strategies, AddOns, multi-account tools, copier components, and risk-aware execution for compatible futures workflows.
NinjaScript / C#
Expert Advisors, account management logic, trade copying, and automated risk controls for compatible MT5 accounts.
MQL5
EA-based execution, account-level controls, copier components, and broker-aware automation for compatible MT4 environments.
MQL4
cBots, account automation, API-connected workflows, trade routing, and account-specific risk logic where supported.
C# / cTrader API
Strategy and indicator alerts routed through webhooks into compatible broker or trading-platform execution environments.
Pine Script / WebhooksExisting products demonstrate practical experience with cross-platform execution and trade routing; custom projects can extend beyond these predefined workflows.
Cloud-Based
New Release
Cloud-Based
Trending
Local
Trending
Cloud-Based
Local
Cloud-Based
Local
Local
Answers about funded and evaluation accounts, risk controls, strategy automation, platform compatibility, and project delivery.
A custom project can combine multi-account execution, trade copying, automated strategies, account-specific sizing, risk controls, alerts, dashboards, and platform or API integrations. The exact scope follows the target workflow and account rules.
Yes. One strategy, master account, or signal source can drive multiple owned accounts with separate sizing, filters, symbol mappings, and risk rules. Account ownership, platform support, and current firm rules must be verified before deployment.
Yes. Daily loss, drawdown, position size, session, symbol, and lockout rules can be configured separately when the target environment supports them.
Yes, when the required automation is permitted by the account and platform rules. We can build rules-aware execution and risk controls around limits supplied for the project, but we do not guarantee challenge outcomes or build systems intended to bypass account, identity, or risk controls.
No. We can start from your account structure, broker or prop-firm environment, strategy or copying workflow, and required controls, then determine the appropriate platform components, APIs, or server infrastructure.
Yes, where the target platform and account rules permit the workflow. TradingView webhooks or other external signals can be connected to supported execution environments with validation, routing, account-specific sizing, filters, and risk controls.
Yes. A trade copier routes existing trades or signals, while an automated strategy contains its own execution logic. A custom project can include either approach or combine both.
Yes. Source code and full IP ownership are transferred on final delivery and full payment unless a different arrangement is agreed in writing for a specific project.
Share your account structure, workflow, risk limits, and target environment. We will review the technical scope and outline the next development steps.