Using Option Omega for testing + Option Alpha for execution with TradingView in between ..am I overcomplicating this?

Hey everyone, Looking for some honest feedback from people who’ve automated options strategies before. Current setup: I backtest strategies in Option Omega (mostly SPX, 0DTE, rules based on GAP up/down, overnight move/VIX, SMAs, intraday move, etc.) For live signals, I mirror the same conditions in TradingView, When all conditions line up, TradingView triggers a webhook alert That webhook goes to my own small web app, the app decides which strategy variant to run (I have 3–4) Applies basic risk rules The app then triggers Option Alpha, which handles: order construction multi-leg execution broker interaction So Option Alpha is still doing execution — I’m not bypassing it today.(Trigger webhook alert).. Why I added my own app in the middle: I want centralized logic. I may have multiple accounts / users in the future Easier to add logging, kill switch, global risk limits Eventually want one signal → multiple accounts with different sizing I can disable or enable some strategies on the fly..even though trading view sends the alert to my app..it decides whether it should forward it to optionalpha or not. Where I’m unsure: Option Alpha already solves execution and broker edge cases, and it’s clearly well-engineered. At the same time, it’s not really built for multi-tenant routing or centralized control across many accounts. So I’m wondering: Is this architecture overkill? I was thinking to use direct broker API (but wondering if it's really required and any benefits).. Would you simplify and let Option Alpha handle more logic? At what point does it make sense to consider direct broker APIs instead of OA? Any obvious weaknesses or failure points in this design? Not trying to build an HFT system or sell anything .. just trying to avoid unnecessary complexity while keeping things safe and scalable.