GUI for Lean

We support custom data files. Mind reporting what is wrong with the bitfinex data to the data issues page?

Local GUI is planned for August.

Hi Jared, thanks for the reply.  August… that's good news.  I'm thinking of creating my own using the .json dump file as a data source.

Apologies if I seem too harsh was just really upset about the data quality

Hi Franky; 

No worries not harsh, we're quants, just provide the data and it'll get fixed. Unsubstantiated claims are generally ignored as misunderstandings or people blaming algorithm issues on the data. To move it forward, create a Data Issue; linking to the precise file and lines in the file you believe are corrupt. This substantiates the claim and gives us something to fix.

We provide 100% transparency into the raw data you're backtesting with - you can look up the file in the Data Explorer. Please try it. 

Jared

Hi Jared Broad ,

Do you have any more information about local GUI coming in august? Is it gonna be web based? WPF? What is the scope of the UI?

Ive looked everywhere in github to find the code to answer my questions by myself but cant find anything related to that UI in github.

As i am starting my own one, i wont waste my time if a similar product is already nearly completion. I could even maybe help a bit on this one.

Thank you

The GUI for August is the same as the QC.com GUI so we can focus our maintenance/feature efforts, but hosted locally. 

Jared Broad 

Wow, and the UI is still fully open source (and free of charge)?

Thats an amazing plus value to lean!!

Thanks for your quick reply and your amazing work!

Sorry no, it will need to be a paid, closed source plug-in to cover the maintenance costs of the technology. We're not sure on the pricing yet but something on the order of $30-60/mo. Similar desktop platforms are on the order of $1000 per year. 

Oh ok, that make sense. Do you have any more information to share at the moment? 

Will this subscription include data, as it does on your saas?

We will still need a paid plan on top of this on quantconnect?

Will it run fully local (can work disconnected)? I mean disconnected from quantconnect, not from the internet ;)

Is lean moving toward more of paid plan or can we thrust the platform to remain as it is, open source and free of charge?

Even though I can understand the move (paid plugin) on a cost management side, lean.io is really missing something on that point, in my opinion. 

Don't you think that might push the community (mostly developers I guess) to roll their own UI to be able to keep a full open source and free of charge platform?

Please don't see those comments / questions negatively, as being a new users, I want to make sure where your product (mostly the lean.io side more than quantconnect) is leading before getting invested too much in there. Obviously I understand the need to get funding in order to maintain the stack but I am afraid that it move to a different business plan where actual users might be forced to use closed source, paid component in order to use the tools successfully?

Thank you

Ps: let me know if I shall open a new discussion instead of keep asking question i here ;)

Most people misunderstand the definition of “free open-source software” - it is free as in freedom, not free as in beer. QuantConnect and LEAN will continue providing freedom to extend and implement anything you want but charge for convenience. 

You're quite free to make a GUI with the stack today; and companies do build their own internal GUI - at the cost of 100+ hours of work. All it requires is investing the time and energy to build it yourself. We do not lock you into QuantConnect, you have the freedom to leave. 

We'll use freedom and convenience to guide our decisions. Most people would happily pay a low fee to save hundreds of hours of work and get started immediately. We can provide that convenience and they can get started immediately. 

Hi Jared Broad 

Yes i fully understand that. 

What i am worried is that at some point, corporation that first maintain an open source stack and get users to get invested in their platform finally decide to move away from that business plan and then the users basically get locked by this provider to pay in order to keep using that stack (using closed source plugin) or have to move away, which include high cost... See what ElasticSearch did not long ago, which led to a fork from Amazon but not without pains… 

I might not have expressed myself correctly as i was not at all arguing against the move but asking question to make sure our move to lean.io (from freqtrade) still make sense and that we wont get into a situation where the core product (lean.io) will stop evolving outside of closed source plugin. 

Please note that both ways are totally acceptable as long as its clearly expressed to the users. 

On my side, i would have been more  open to some kind of donation, patreon etc form of remuneration for an open source UI that i know would be available as is for the long term than being locked in with a closed source plugin. But here, its only a personal opinion. 

All that said, you and your team probably built one of the best quant platform around and for that, congrats!

Thank you, 👌 No problem asking questions, we've got a track record of 10 years now we can let that speak for itself. After 10 years of building the best platform in the world, we released the LEAN CLI – a fully local version of LEAN to make it even easier to leave QuantConnect 😁.

Our continued single focus is making something epic for the community and we trust the growth of the ecosystem ("the whole village") will raise all boats, and institutions will realize its 100x cheaper to build with LEAN, growing the number of paid institutional level products we can distribute to support the community as a whole. 

Dominic Lapointe 

If need be there are some community alternatives which are open-sourced. There is one which works with WFP (called Algoloop Capnode, though it seems it was taken off GitHub) for Windows as well as one I had made (https://github.com/aarjaneiro/QtLean) for Mac and Linux. The fact that both major open-sourced GUI projects work on a separate set of systems, however, highlights why creating a GUI for Lean is not very easy: the .NET ecosystem can be difficult to work around in a generalizable manner. 

I reckon it would not be impossible, but it would be a daunting task (as mentioned by Jared Broad) to develop a FOSS, professional grade GUI which works across the board. The Unity game engine, after all, works splendidly across systems and comes from a largely C#-based stack (although it is not a FOSS project).