Support Board
Date/Time: Thu, 22 Oct 2026 15:42:47 +0000
Commercial ACSIL study with local desktop-app dependency
View Count: 369
| [2026-09-05 04:42:41] |
| FuturesBod - Posts: 31 |
|
I am developing a commercial ACSIL custom study/DLL which I intend to distribute using Sierra Chart's authorised-user/custom-study distribution system. The DLL would require a separately installed Windows desktop application on the same computer. The ACSIL DLL and desktop application communicate only over localhost. Is this type of commercial custom study permitted by Sierra Chart's distribution/authorisation rules? I am only asking whether the dependency on a separate local desktop application is permitted. [For context, its a position management tool grabbing data from Sierra for the separate application] |
| [2026-09-05 23:11:42] |
| Sierra_Chart Engineering - Posts: 25243 |
|
This is definitely a major concern for us due to exchange rules: grabbing data from Sierra for the separate application]
Our formal answer is no, this is not permitted. If the data is used within Sierra Chart within a custom ACSIL study loaded by Sierra Chart, that is fine. If you can keep the data within the ACSIL study that is fine. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2026-09-05 23:12:44
|
| [2026-09-06 00:38:06] |
| FuturesBod - Posts: 31 |
|
Oh of course - I see why that kind of use of the data would be a concern - no it shouldn't be that but I can clarify exactly what is does nearer the time. Its using the trader's position data. Its early design stages and the reply helps me with that - especially the keeping it within the study part. Thanks! Date Time Of Last Edit: 2026-09-06 01:19:24
|
| [2026-09-06 13:36:12] |
| FuturesBod - Posts: 31 |
|
After reading your comments and CME Group data-use licensing the previous design would have breached the CME rules but I think the following is the case and would still work for the app: **FORBIDDEN OUTSIDE OF SIERRA/ACSIL ** - Any live CME data (last traded price, bid/ask, etc.) - Any data that could be used to derive live data (e.g. live position PnL) - Automated/Semi-automated/Manual order commands that open, close or amend orders/positions **ALLOWED OUTSIDE OF SIERRA/ACSIL** - Order fill information (quantity, and price of transaction) - Current position Size - Calculations based on that static information sent to Sierra/ACSIL So an external app is allowed to ask for the fills and current position because that is static 'account state data'. The app can perform calculations (e.g. some meaningful price level) and it is allowed to send that back to Sierra/ACSIL. For clarity, it sends the static calculated level only, not an order, only the number which can be updated only on new order fill/position size information. Sierra/ACSIL code can read that price level and does the actual live position management/orders etc/ all within ACSIL so no CME live data leaves Sierra, ever. The idea (if there is demand) is to license the app and control access to the ACSIL dll via Sierra Chart's authorised-user/custom-study distribution system. Can you confirm if this architecture is acceptable? Date Time Of Last Edit: 2026-09-06 13:48:28
|
| [2026-09-08 22:13:19] |
| Sierra_Chart Engineering - Posts: 25243 |
|
We will get back to you on this.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: