I've been building DepthSight for the past year - a self-hosted algorithmic trading platform that you run entirely on your own hardware, so your API keys and trading logic never touch a third-party server (like 3Commas or Veles).
Instead of writing code, it features a drag-and-drop node editor (40+ logic blocks) where you can build complex strategies, cross-reference indicators, and manage risk dynamically. It also includes an AI assistant that can generate strategy structures from text prompts or even screenshots of chart setups.
Since Lemmy is built on federation, I thought you guys might appreciate the architecture: DepthSight nodes can opt-in to connect to a central Federation Hub. This creates a community network where self-hosted nodes can share verified strategy templates, discuss trading ideas, and form a global node topology map.
Features out of the box:
- Visual strategy builder
- Federation Hub
- Dual backtesting engines
- Dynamic risk management that adapts per trading pair
- Multi-tenant support (JWT, Redis quotas) if you want to host it for others
Stack: FastAPI, Celery, Redis, PostgreSQL, React (with a mobile-optimized PWA). AGPLv3 licensed. Runs with a single deployment script (curl | bash).
Github: https://github.com/DepthSight-Pro/DepthSight
Built this solo (heavily leveraging LLMs for the heavy lifting in code generation). Would love to get some feedback from the self-hosted community, especially on the architecture or features you'd want to see added!
If you used a llm to generate code, how are you licensing this under AGPL? LLM output is not copy-protected.
Thats only partially accurate btw. I see this comment often lately so I think its worth clarifying.
If its wholly generated, then it is not copy protected, and its in the public domain. If it has human guidance (beyond entering prompts, and actually editing the code), it is. Note that this is also in the US only, and obviously subject to change. I'm not personally sure of the consideration of copyright elsewhere.
That's a valid legal question.
The AGPLv3 license applies to the repository as a whole (the software architecture, the visual logic blocks, the UI/UX, and the compiled system). The license is there to establish a rule: if someone takes this infrastructure, modifies it, and hosts it commercially for others, they are legally obligated to keep their modifications open-source.
That being said, I don't harbor any illusions. I am well aware that in the real world, bad actors might just fork it, strip the license, and run a closed commercial service anyway. But having the AGPL in place is a statement of the project's ethos and gives at least some baseline legal leverage if a larger corporation tries to blatantly rip it off.