About POLARIS
About POLARIS
How our work took shape
POLARIS brings together trading research, MQL development and portfolio analysis. Our approach grew from turning market observations into rules, testing those rules and working through the differences between a report and real execution.
01Story beginning
Where the work began
Origin
From market observations to testable rules
The story began around twelve years ago in gold futures. Programming offered a way to describe trading ideas precisely and test them in MQL.
A promising backtest was encouraging, but using a system exposed other questions: changing spreads, different price feeds, execution delays and settings that worked only in a narrow range.
That experience changed what we looked for. Alongside the return, we began asking where the result came from, how sensitive it was and what could make the system fail.
We share this work through research notes, system profiles and portfolio reports, including the limits that matter when someone tries to use the results.
02Experience
Experience behind the work
Experience
Engineering, market research and client projects
Our team combines engineering and programming with practical market work. Client projects have brought us different brokers, trading styles and operating requirements.
≈12Y
Market research
The work began in gold futures, with a need for clearer signals and repeatable rules.
2016
MQL development
Research and programming became an ongoing professional activity.
170
Development archive records
A record of projects and research across strategies, indicators, tools and tests; not a count of profitable systems.
01
Engineering background
A core member holds a bachelor’s degree in Electrical Engineering–Control and a master’s in Electrical Engineering–Power. That training supports a practical habit: define the problem, test its parts and investigate failures.
02
International client work
Projects have served clients in Asia, Africa, Europe and Latin America. A core member has also continued research from a Dubai office for more than five years.
03
Practical system development
The work spans grid and martingale models, Renko and directional systems, indicators, trade managers, dashboards and portfolio risk controls. Each has different execution needs and ways of failing.
03Method
From individual systems to portfolios
Method
Looking at how systems behave together
Strategies depend on different conditions: trends, ranges, volatility or particular price relationships. Combining them means checking when they may lose together.
We review each system’s role, position sizing, shared exposure and execution needs. Monthly reviews using rolling data windows help us look for concentration and changes in behaviour.
Diversification and periodic review do not prevent losses or guarantee better returns. Their value depends on the systems selected and how they are used.
The questions behind a result
These checks help expose weak assumptions. Each system’s records should make clear what has been tested and what remains uncertain.
- 01
A market idea
Start with an observation and explain why the proposed rules might work.
- 02
Explicit rules
Define entries, exits, position sizing and exceptional conditions so the logic can be checked.
- 03
Historical coverage
Include varied market conditions and, where suitable data exists, more than ten years of history. State the actual coverage.
- 04
Sensitivity to settings
Check nearby parameter values and sensible ranges, rather than relying on one attractive combination.
- 05
Data and execution checks
Compare broker and Dukascopy data where available, and examine the effect of small price, timing and execution differences.
- 06
Data held back from development
Evaluate on data that was not used to build or calibrate the system.
- 07
Observation in live conditions
Observe spreads, slippage and operating behaviour over several months where records are available. Keep demo and real-account results clearly labelled.
04Story end
What guides the work
Principles
Four things we keep checking
01
A reason for the rules
Explain the market idea before searching for parameters that improve a backtest.
02
Combined risk
Set risk limits and exit logic, then review the exposure created when several positions are open together.
03
Results with context
Keep backtest, forward, demo and real-account records distinct, with their dates, conditions and limitations.
04
Review after release
When behaviour changes, investigate the cause and document the reason for any update.
Make the experience useful
Our research notes, system profiles and portfolio reports explain the decisions behind the work. We want readers and clients to understand both the results and the practical limits.
How an engagement starts
POLARIS provides trading and strategy consultation, custom algorithmic development and guidance on the sample portfolios shown here. Each engagement begins with an individual discussion and agreed scope, deliverables and fees.
Story endTell us about your project
Describe the problem, what you already have and the result you need. We will review the request and discuss a suitable scope.