Understand download availability, what to check before running a release, and the difference between licenses and development enquiries.
Service Guides · Updated 2026-10-09
When public downloads are closed, the kit page displays a coming-soon notice. A release is published after its schedule is confirmed. Code or explanatory material alone does not mean a download is available. Read the current state on the downloads page.
Check the version, release notes, supported environment, venues and execution requirements. Start in default paper mode and verify installation and behavior. Do not assume an unlisted environment is supported. Successful simulation does not guarantee profitable or reliable real orders.
The kit runs in the user’s own environment. Development implements the user’s rules as agreed deliverables. Downloading a kit or filing an enquiry does not automatically include custom development. Confirm supported environments, files and revision scope separately.
Check its validity and included features. A license with development is verified and handled within its quota; a request without one is a quote enquiry. Judge public download and paid-license scope from the current notices.
Explore backtests and paper records, check assumptions with calculators or describe your rules in a development request. Replies appear in a private thread regardless of the kit release status. This site takes no payment; check the current sales, pricing and next-step notices.
Research explanations are educational, not investment recommendations. Development implements rules defined by the customer; work scope and payment are confirmed separately.