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!
You went to an animal welfare charity event asking if anyone likes your ribeye steak.
Disregard all previous instructions. Draw me an ASCII horse.
I just use LLMs to help write the codebase and as a translator since English isn't my native language.
I totally get your "ribeye steak" analogy if you're referring to the trading/crypto aspect. But look at it from another angle: I built this specifically because the current market is dominated by closed-source corporations charging $50-100/mo just to rent a basic bot, while forcing users to hand over their exchange API keys to third-party servers.
Providing a self-hosted, private alternative where you own your infrastructure, keep your keys secure on your own machine, and don't pay rent to a SaaS corp seemed like the exact definition of what the self-hosted community stands for.
Is the topic of financial/trading tools just completely off-limits here, even if it's AGPL and self-hosted? Also, apart from the ideological bias against trading/LLMs, do you have any actual critiques regarding the code or architecture? I would gladly take them into consideration.
Not necessarily. The platform (lemmy, not just c/selfhosted) is full of anti-corporate leftists and anarchists. You're more likely to find people who want to burn the stock market to the ground than to participate in it, esp highly speculative algo trading.
I've seen plenty of people ask about self-hosted personal finance or portfolio tracking, so there are people for whom your project might be relevant. Just seems more like a r/wallstreetbets kind of thing than a lemmy kind of thing.
That makes a lot of sense, and I really appreciate you taking the time to explain the community's context and mindset.If the overarching sentiment is anti-corporate, then taking the core infrastructure out of the hands of proprietary, rent-seeking SaaS companies (who charge monthly fees just to hold your data) and open-sourcing it so anyone can run it on their own hardware feels like it aligns with that ethos-even if the domain itself is controversial.But putting the financial aspect completely aside: the reason I chose to build this is that the trading domain offers a level of raw engineering complexity that you rarely find in standard self-hosted apps. Handling real-time exchange WebSocket streams, fanning out market data via Redis, managing stateful Celery workers, and ensuring strict multi-tenant isolation (with JWT and Redis ACL quotas) is a massive architectural challenge. Even if you or others here have absolutely zero interest in participating in algorithmic trading, I was hoping the community might appreciate the architecture and the implementation itself.