IBC VS ib-controller

I would start here. https://github.com/IbcAlpha/IBC Using slightly modified code running in docker container on linux server.

Interactive Brokers has been the best I've found for that. You do have to use their platform, but that allows you to focus more on writing your algos and less on re-inventing security and such. There are solutions out there to keep the gateway connected. see: https://github.com/IbcAlpha/IBC

And also use IBC to keep it connected. I've had issues where the daily maintenance performed on their servers causes IBGateway to pop up a dialog before continuing. IBC handles all those issues.

I used to have this problem but have since started using IBC, along with Task Scheduler, to handle all those connectivity issues on Windows. It all supports *NIX-based systems, too.

Actually I found it https://github.com/IbcAlpha/IBC

There are few autorunner scripts that worked well with previous versions of TWS (901-963) by automating it and even running them headless. However, with the latest version of TWS, it is hard to do.

I recently installed this https://github.com/IbcAlpha/IBC It preforms auto logon to IB TWS. Works fine. It generates a batch file, place it on desktop and I included my charting program. One click both open and IB user name and password entered and TWS opens. Magic. Was recently updated.

Look at https://github.com/IbcAlpha/IBC for gateway automation.

To automatically run TWS or the gateway https://github.com/ib-controller/ib-controller but it honk there’s a more recent fork

The main drawback, which I havent looked into yet, is how to keep the IB Gateway up and running for prolonged periods, as it restarts / needs a relog every day / week. But there's multiple solutions to that. IbController comes to mind (https://github.com/ib-controller/ib-controller), as well as IBC (https://github.com/IbcAlpha/IBC). So I know there's solutions, I just havent bothered looking into it.