no additional sub required from my current experience.

1 account per type of account (retirement, tax free and margin - I'm in canada), but 1 secondary user for each account, said secondary user being that used in Quantopian.

As for handling multiple strategies: From my POV, this has to be done programmatically. I've currently spent most of my time designing the framework for syncing trading orders between sub-strategies, the main process's job (handle_data) being capital allocation to strategies, and the syncing component.

happy automated trading

Florent is right, the main key is to use the IB 2nd users for each Quantopian algo.
This was confusing for me, I have two IB accounts, so to try to help, I'll elaborate on setting that up.

1. Log in to IB with your main IB account username, password (and the extra security mechanism), at this point, the only username, perhaps .
   
2. At the bottom of the screen you'll see the account ID that you are currently accessing.
   
3. Manage Account > Access Rights > Users > 2nd user.
   
4. Go thru the process of setting up a second user.
   
5. At the bottom of the screen, click to switch accounts.
   
6. Repeat steps 3 and 4 to set up a 2nd user for that second account.

Start your Quantopian algorithms using the 2nd user username/password for each account.

Now you can log in to IB separately in a browser using your main IB account username, password (and the extra security mechanism), without causing either algo to be logged out automatically.

Ah yeah, I was rather hoping to avoid having to do inter-algo syncing and allocation to start with, just keep things super simple by giving each algo its own sandbox. EDIT: I should add, because I would like to use order_target_percent also to keep things simple. But I suppose if I give up on (or manage my own) compounding, I could write my own variant of that which kept to its own capital. Still, it seems safer to set up separate accounts, no?

multi-strategy using order_target_percent: A simple example I wrote few weeks ago ;-)
https://github.com/florentchandelier/zipline2quantopian/tree/master/example/multi-strat_multi-instru

same post on quantopian: https://www.quantopian.com/posts/designing-a-multi-strategy-portfolio-in-zipline-for-quantopian

2 cents: It depends on you objective: I have different set-up if I manage retirement funds, tax-free accounts and my usual margin ... in terms of risks but also in terms of managing tax on gains/dividends. One strategy means pretty much nothing for me, but a combination of multiple strategies sounds more like it ... thus the framework.

Currently, I see more value in building the appropriate framework for handling such multi-strat, rather than getting into elaborated strategies ... eventually because my objective is managing my funds.

In the end, maybe a multi-strat will make it up to the contest ;-)

HTH

Speaking from personal experience, you may find that the IB account teams are confused as to why someone with an "Individual" account is opening so many different accounts of the same type. Once you explain it, they're cool, but it can introduce delays in the account provisioning process.

On a related note, it would be super cool if Quantopian could somehow integrate with IB's "Model Portfolios" feature (which is technically only available to advisors, but just about anyone can get a Friends and Family advisor account). That feature allows sandboxing different strategies within the same account, or across multiple accounts if you want to run the same strategy on, say, a portion of both your cash account and your IRA account. No idea if that is possible. But it would be neat.

Would love to let friends and family run my code independently on their own broker account without being able to see my code.

Image credit clipartpanda.com

Whoa ! How do you add images inline?