u/arpand

Recently I worked with a client who already had a proprietary trading strategy and wanted to automate execution through Interactive Brokers.

It was turning their existing strategy into a reliable execution system — connecting Moomoo/AmiBroker-style strategy validation with IBKR execution — without requiring the client to disclose the parameters that actually make the strategy proprietary.

The setup included:

• SAR Parabolic + Bollinger-based signal detection using raw OHLC data
• Candle-by-candle signal validation against Moomoo and AmiBroker
• Automated options execution through the IBKR TWS API
• Strike and expiry selection based on predefined rules
• Exit orders calculated from actual average fill price
• Real-time position monitoring
• Multi-account replication using the IBKR Advisor account structure
• Telegram notifications for entries/exits
• Mobile manual override for adjusting exits or cancelling trades
• Emergency kill switch

Curious how others building proprietary strategies on IBKR handle the gap between strategy/charting tools like AmiBroker or Moomoo and actual automated execution through IBKR?

Recently I worked with a client who already had a proprietary trading strategy and wanted to automate execution through Interactive Brokers.

The interesting part wasn't inventing the trading strategy.

It was turning their existing strategy into a reliable execution system without requiring them to disclose the parameters that actually make the strategy proprietary.

The setup included:

• SAR Parabolic + Bollinger-based signal detection using raw OHLC data
• Candle-by-candle validation against the client's Moomoo charts
• Automated options execution through the IBKR TWS API
• Strike and expiry selection based on predefined rules
• Exit orders calculated from actual average fill price
• Real-time position monitoring
• Multi-account replication using the IBKR Advisor account structure
• Telegram notifications for entries/exits
• Mobile manual override for adjusting exits or cancelling trades
• Emergency kill switch

One part I'm particularly happy with was the Secrets Manager.

The client could configure the sensitive parameters behind the strategy, while those values remained hidden from me. I could build, deploy and maintain the execution infrastructure without knowing the client's proprietary configuration.

Curious how others building proprietary strategies on IBKR handle this separation between strategy IP and the people maintaining the execution infrastructure?

We recently worked on the product design and technical foundation for a purpose-specific consumer lending platform.

The original opportunity did not move forward, but it raised an interesting product strategy question.

The platform covered areas such as:

• Borrower eligibility and application workflows
• Document and income verification
• Configurable underwriting rules
• Loan servicing and repayments
• Delinquency and hardship workflows
• Borrower and operations dashboards
• Audit logs and role-based access
• Integrations for banking data, identity verification, payments and e-signatures

The original use case was highly specific. Technically, many of the workflows could be adapted for other lending programs, but regulated lending products are heavily influenced by each lender’s policies, compliance requirements and existing systems.

For people who have worked with lending platforms, CDFIs or credit unions:

How reusable is a custom lending platform in practice?

Is the underlying workflow and architecture valuable across multiple lending use cases, or does every implementation become so dependent on the lender’s policies that rebuilding is usually more practical?

I would be interested in hearing about real implementation experiences, particularly around underwriting configuration, compliance and servicing.