Elliott platforms and services: compare the actual workflow
NinjaTrader, MotiveWave, Sierra Chart, Quantower, cTrader, ELWAVE, WaveBasis, EWI, ElliottWaveTrader and LuxAlgo under one evidence record.
Published: (UTC+3)
Русский · English · Deutsch · Español · Français · Italiano · 繁體中文 · 日本語 · 한국어
This is an editorial reading of public vendor documentation on 25 October 2026, not a report of installed-product testing or a ranking by returns. A manual drawing, an automatic study and an analyst subscription deliver different outputs. Compare each against the same task and current access conditions; the commercial product claims linked below remain vendor claims.
A comparison record before choosing a product
First save source, instrument, timezone, adjustment basis, completed-bar cutoff, version, edition, settings and manual changes. The two invented six-point inputs below differ only at P4. In an ordinary upward impulse,119 overlaps wave-one territory ending 120;125 avoids that particular violation. A tool able to draw both has not necessarily validated either. Ask what it checks, which alternatives remain, and when each label became available. An invoice, screenshot or accurate-looking target does not establish predictive performance.
| P0 | P1 | P2 | P3 | P4 | P5 | Selected check |
|---|---|---|---|---|---|---|
| 100 | 120 | 110 | 145 | 119 | 150 | P4=119 < P1=120 |
| 100 | 120 | 110 | 145 | 125 | 150 | P4=125 > P1=120 |
Does drawing 119 validate an ordinary impulse?
No. The non-overlap check fails; other structural checks remain separate.
NinjaTrader 8: a community manual drawing tool
The Ecosystem entry identifies a third-party manual Elliott drawing based on Path tools. Its published workflow selects Ewave after import, places points and completes a three- or five-wave object; properties control degree and ratios. That describes annotation. Before treating a separate automatic indicator as equivalent, record its author, version, buffers, settings and confirmation rule. A manual label placed on the 119 example does not repair overlap. This review neither installs the add-on nor attributes it to the platform’s native automatic detection.
MotiveWave: static count, dynamic study and scanner
The official guide distinguishes manually placed components, static Auto Wave/Auto Analyze and the dynamic Auto Elliott Wave study. Follow the documented study route when testing updates; save the selected data window before adding a completed bar. Compare a fresh result against the saved one rather than calling every revision an error. The guide places Elliott scanning in Ultimate. Edition and mode therefore belong in the comparison record; a static snapshot and a dynamically recalculated count are different tests.
Sierra Chart: establish the exact tool
Current feature documentation lists drawing and price-projection tools. A dated 2022 support answer said there was no built-in Elliott drawing tool; it does not establish every later version or third-party extension. Specify the actual study/add-on rather than calling every ZigZag or retracement an Elliott indicator. Record the selected anchors, price units and algorithm, then replay the 119/125 cases and a newly completed bar. Missing evidence about automatic wave validation stays unverified; it is not a measured product failure.
Quantower: drawing versus calculated output
The documented chart sidebar separates drawings, indicators and overlays. Begin by selecting symbol, timeframe and history depth, then record which object or indicator was added and how it was created. A drawing API or an attractive polyline alone does not establish automatic Elliott recognition. For a claimed Elliott extension, retain its identifier, author, parameters and pivot availability; repeat the same input and inspect changes. The general chart documentation does not prove the behavior of an unnamed third-party wave detector.
cTrader: wave objects do not prove a count
The Algo reference names impulse, correction, triangle and combination chart objects. They represent ordered labelled pivots; the degree controls notation. Choose the actual object and save its pivot times and values. A six-point impulse drawing can display the 119 sequence while its ordinary-impulse price check fails. Identify a separately claimed detector or cBot by source/version and examine its rules; do not infer automatic recognition, profitable signals or an order execution from the existence of a chart object.
ELWAVE: compare the module and input contract
ELWAVE advertises automated analysis and vendor-data integration; its FAQ separates modules. Compare the exact licensed modules and data format against your task, not the brand name alone. The FAQ’s historical-replay route truncates future input before analysis and then reveals later points. Preserve that cutoff and the original result when evaluating it. Old FAQ operating-system examples are not current compatibility evidence. No vendor claim of completeness or forecasting quality is treated here as an independently measured success rate.
WaveBasis: window, bias and alternatives
WaveBasis documents AutoCounts with selectable date ranges and count bias, and plan-dependent subwave alternatives. Save those settings before running a count, then inspect which waves are unresolved and how an alternative changes the proposed structure. A different window or bias changes the experiment. Use the same price file and completed-bar boundary when comparing another platform; a visually similar market name does not guarantee identical inputs. Vendor descriptions of likely counts are not an independent calibration study.
Elliott Wave International: education and analysis access
EWI’s education page separates freely readable resources such as Waveopedia from books, courses and subscription services. Choose whether your task is learning a definition, checking a cited page or reading a dated analyst report. Record author, issue time, market, scenario and later revision. Compare an educational source with the corresponding need; do not score an analyst subscription as if it were a locally installed counting engine. A historical publication or selected successful example alone cannot supply a complete performance denominator.
ElliottWaveTrader: member access and review evidence
ElliottWaveTrader’s public site offers analyst commentary and member access; its official login is linked here. Open the publisher’s own domain for an existing account and keep access problems separate from analysis quality. This editorial comparison does not claim a paid-room test or reproduce a customer testimonial. For a review, preserve dated original and revised scenarios, all qualifying cases and costs before measuring an outcome. A publisher-selected testimonial and an independent complete trading record are different evidence.
LuxAlgo: the exact library script and pivot settings
The linked LuxAlgo Library page describes its Elliott script, pivot sources, ZigZag length and invalidation markings, and labels this build free. Record the exact build and settings; that statement does not grant every paid service or every platform entitlement. Test when the pivot became knowable and how a later extreme changes labels. A visible Fibonacci zone or crossed-out pattern is output to inspect, not proof of future profit. Compare the script with the same completed input used for the standalone workflow.
Zerodha and ForexFactory: identify the actual drawing workflow
Zerodha’s official ChartIQ feature page lists Elliott wave among drawing tools. That establishes an annotation feature; it does not establish an automatic wave-counting indicator or a measured success rate. Save the actual chart, tool, anchor times and prices before comparing its output with a separate detector. A drawing of the 119 overlap example remains subject to the same price rejection.
The linked ForexFactory MT4 thread began in 2010. In its follow-up, the author describes manually placing and naming trend lines; this is evidence about that particular thread, not every current MT4 add-on. An attachment, download count or forum recommendation does not establish current compatibility, a licence or automatic validation. No attachment was downloaded or executed for this note. Identify the exact file, version and buffer contract before treating a separate custom indicator as equivalent.
| Source | What is documented | What remains unestablished |
|---|---|---|
| Zerodha ChartIQ | Elliott drawing tool | Automatic wave validation |
| ForexFactory 2010 thread | Author describes manual line placement | Current binary behaviour or performance |
Open source and Nifty: separate code, licence and data access
The public alessioricco/ElliottWaves repository describes Python pattern recognition and an ElliottWaveFindPattern interface with a source dataframe, measure, granularity and date bounds. Its LICENSE identifies MIT and Alessio Ricco. This is a concrete source-code and licence record, not a tested installer, a verified complete Elliott engine or a profitability result. The code was not executed here. Pin the commit and preserve the exact input and settings before undertaking a separate evaluation.
For a Nifty free-download search, keep three questions separate: may the code be used under its licence, can the intended Nifty series be obtained under its own access conditions, and does the chosen implementation accept that series correctly? A free repository or a free-marked script grants no exchange-data entitlement and does not establish a configured Nifty workflow. Record spot index versus futures, the actual symbol and provider, session, timezone and completed-bar cutoff; use the existing India preflight and Nifty source case. Compatibility and returns remain untested rather than being inferred from “open source”.