I built AlertHype — a lightweight TradingView alert router for Telegram/Discord
Hey IH 👋
I just launched AlertHype, my first side project that I’m trying to turn into a small paid product.
Why I built it:
I was running trading automation on Binance Futures (ccxt) and constantly missing or mismanaging TradingView alerts.
I tried existing tools, but most of them felt too heavy for my use case — either required VPS/setup, were expensive for just forwarding alerts, or had way more complexity than I needed.
So I ended up building something simple myself.
What it does:
It routes TradingView webhook alerts → Telegram or Discord.
Paste a webhook URL, connect, and it just works — no server setup, no code.
Current state:
Launched ~48 hours ago
0 paying users (still early 😅)
Free plan available (no login required)
Pro plan: $9.99/month (alerts, logs, customization, etc.)
What I’m trying to learn right now:
Where traders actually hang out / how to reach them
Whether the pricing feels reasonable
What would make this a “must-have” instead of a nice-to-have
Would really appreciate any feedback — especially from people building in trading / automation space.
If anyone wants to check it out:
👉 https://alerthype.com
Thanks for reading 🙏
You probably built the right product for the wrong emotional frame.
Most traders do not wake up wanting “alert routing.”
They want fewer missed entries, fewer late reactions, and less anxiety around execution.
“Webhook forwarding” sounds infrastructural.
The actual value is confidence and speed during live volatility.
That distinction matters because your current positioning makes the product feel optional.
Also: AlertHype is descriptive enough to explain the category, but it also sounds temporary/tool-ish for something sitting in a trading workflow.
If this grows beyond forwarding into execution infrastructure, monitoring, or automation reliability, the current name may start capping perceived seriousness pretty quickly.
Vroth.com would fit that future direction much better.
Harder edge, more durable, more infrastructure-grade than AlertHype.
That’s a really good point — I agree the emotional side matters more than the technical framing.
Right now I’m keeping it simple because I’m still validating the core use case, but I’ll definitely rethink how I position it as I learn more from users.
Appreciate the feedback — that’s really helpful.
Happy to answer any questions or go deeper on how I built this.