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!
@DepthSight@lemmy.world you made this post right in the middle of a bigger conversation around promotional posts, so be aware that this post may be removed later pending the outcome of that discussion in the meta thread here:
https://lemmy.world/post/48462124/24369166
For everyone else, here is why I’m leaving the thread up:
Here is where I see a potential problem:
For those coming here and reporting, please be aware this doesn’t blatantly break any rules imo, only the (extremely subjective) rule 2, which I don’t think fits for the reasons I noted above. Making a good reference for discussion in the meta.
Hi @curbstickle_lw, thank you for stepping in and for taking the time to actually look at the project instead of just auto-deleting it based on reports!
I did read the meta thread, and I completely understand the community’s frustration with closed-source, paid advertisements.
To be completely transparent about the two points you raised:
I really appreciate you giving the project a fair look and making a distinction between actual open-source projects and corporate spam. I’ll gladly stick around to answer any technical questions!
The key word there is “community”. You’re not part of this community, you just came here to shill your AI slop.
Calling an enterprise-grade platform featuring a 40+ node visual graph editor, dual backtesting engines, and full multi-tenant isolation “AI slop” just because an LLM accelerated the syntax development is pure ideological gatekeeping. This “slop” objectively outperforms every proprietary $100/mo trading SaaS and basic CLI script in existence right now. If you have an actual architectural critique regarding the FastAPI/Celery setup, the PgBouncer integration, or the Redis ACL security model, I’m all ears. Otherwise, you’re just yelling at a cloud.
Evolve. Or Don’t Look Up.
Except you use JWT’s for auth, which is idiotic and a security nightmare. No enterprise that cares about security would ever accept this.
More info: https://gist.github.com/samsch/0d1f3d3b4745d778f78b230cf6061452
There are other problems, some of which I can see… and some of which I can’t. The problem is that I am not a comprehensive expert, I can only spot a few things here and there. Even if I was an expert, why would I audit your software for free lmao? Pay me for that shit.
What I do know, is that vibecoded apps are bad at security. Many, many vibecoded apps have been hit by horrific security bugs like remote code execution, xss, or authentication bypasses. That shit is simply unacceptable and should be extremely rare in modern apps. The fact that I’m not skilled enough to find them reliably makes me even more cautious and concerned around apps like yours.
It’s not just about the app architecture, but also about you. When a known community figure creates an app, I have confidence that they will have a good security posture and architecture. With vibecoding… not so much.
Nice bait, but the problem is this: Just because you get people to
audit“critique” your software, doesn’t fix the root cause of those problems — you. Just because you manage to re-vibecode the app to not use JWT’s or to fix any other number of issues someone would point out, doesn’t actually mean more issues exist that that person missed. Like if someone specialized in python, then they might miss database issues, and so on. The second problem is that inevitably, you will expand this software, adding more features… and vulnerabilities. That is to say, even if you manage to fix the architecture and security now, you have not demonstrated the requisite skill needed in order to keep it fixed.Criiiiiiingeee
Self righteous self promoting new account that uses AI to write posts for them and is proud about it.
Criiiiiiingeee
ew why are you so toxic and arrogant?
I wanted to upvote you, cause I am not psrt of the anti-ai mob, but then I read you last sentence and the rest of this thread and holy fuck are you unlikable and unbearable.
You asked for feedback and that’s what you got. Don’t get pissy when it’s not what you were hoping for. It’s pretty clear that your project is not welcome in this community.
Ooh, I made you mad enough to use your own words instead of telling the chatbot to write your reply! I’ll do it again: Slop.
Actually, I’m still using an LLM to write this, since English isn’t my native language (as I mentioned earlier).
It’s a pity that, unlike an LLM, you clearly didn’t grasp the reference at the end of my last message. You should probably paste it into one of them—they’ll gladly explain it to you.
I grasped it, I just ignored it. Unlike you, I can use my brain to understand things without having a computer explain it to me.
You are right, though, I should have recognized that awkward mic-drop attempt for the slop tell that it was.