Strategy Engine
Loads a strategy definition and coordinates each processing cycle. Keeps state (open positions, counters, timers) consistent so rules evaluate against an accurate picture.
Our Technology
How TimeXtrade builds trading systems
TimeXtrade builds rule-based trading software from modular parts. Each module has one job, data flows in one direction, and every decision is logged. This page explains each part in plain language.
What is a trading strategy engine?
A trading strategy engine is the software component that holds a strategy's definition and runs its processing cycle: read data, evaluate rules, produce signals, apply risk checks, and hand approved instructions to an execution component. It is deliberately separate from data collection and from order routing so each part can be tested on its own.
Modules
The building blocks
These are the components TimeXtrade develops and combines. Not every project needs all of them.
Backtesting
Replays historical market data through the same rule logic used live, so an implementation can be checked against its specification. Supports transaction-cost and slippage assumptions. More on backtesting →
Risk Engine
Enforces position limits, exposure caps, maximum-loss limits, trade-count limits and time-of-day rules. Sits between signal generation and execution so nothing is sent that breaks a limit.
Execution Infrastructure
Takes approved instructions and submits them to a supported broker/API environment, handling acknowledgements, retries and error states — where and as the applicable framework permits.
Monitoring
A dashboard for system status, open positions, recent signals and health checks, so an operator can see what the system is doing at a glance.
Trade Logs
An append-only record of every signal, risk decision, order attempt and system event, with timestamps, for review, reconciliation and troubleshooting.
Server Deployment
Runs the system on a server so it operates on schedule without a desktop machine being on. Includes process supervision and restart handling.
API Integration
Connectors for supported broker and data APIs. Availability depends on whether the provider exposes a suitable API and on the rules that apply to automated order placement.
Security
Credentials and API keys are kept out of source code and stored with access controls. Transport is encrypted. Access to dashboards and logs is authenticated.
Scalability
Modules can be run as separate processes so that data handling, strategy evaluation and execution scale independently as the number of strategies or instruments grows.
Data Flow
One direction, end to end
Market Data
Collect and normalise price and reference data from supported sources.
Strategy Engine → Rule Processing
Evaluate entry, exit and filter conditions against current and historical data.
Signal Generation
Produce structured intents when conditions are met.
Risk Controls
Apply limits and filters before anything is acted on.
Execution Layer
Route approved instructions to a supported broker/API environment.
Monitoring & Logs
Record every step for review and troubleshooting.
Language we avoid
TimeXtrade does not describe its technology with terms like "ultra-low latency", "zero slippage", "guaranteed uptime" or "institutional-grade" unless a specific, verified basis exists for the claim. Performance depends on your infrastructure, your broker, your data source and market conditions.
Live trading is framework-dependent
Any live order-placement functionality is subject to the applicable broker, exchange and regulatory framework, and to the terms of the broker's API. Feasibility is assessed per project.
Have a strategy to implement?
Bring your documented rules and we will map them onto these modules.