Support Board
Date/Time: Thu, 22 Oct 2026 16:49:21 +0000
Post From: Commercial ACSIL study with local desktop-app dependency
| [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
|