TradersHub
“Market signals as an API, TradingView indicator, or Telegra
Three months ago I knew nothing about web dev, APIs, or cloud infrastructure. I'm a retail trader — 17 years of screen time — and all I had was market logic I trusted and a stubborn streak.
Today TradersHub is a real, working business. One detection engine, three ways to use it. $0 revenue so far, but every part that needs to work, works.
What exists:
API (live) — signals, sentiment, multi-timeframe, health endpoints. Works across stocks, crypto, forex, indices, commodities. Free tier: 3,000 calls/month, no card. ~600ms median response. 6 developers using it right now. This is the only piece generating real activity.
TradingView indicator (coming) — EMA-50 + swing structure + order block zones. Finished and proven on my own charts; holding launch until quality is bulletproof.
Telegram alert scanner (coming) — same engine, delivered as messages on 18 curated markets every 4 hours. Free, low-noise. Scanner is live; channel opens after a week of real-data validation.
The stack I learned from scratch:
Cloudflare (DNS, Pages, Workers, CDN), FastAPI backend, Zuplo API gateway, RapidAPI listing, PayPal subscriptions, a Worker scanning markets 24/7, automated health monitoring, GitHub. No course, no hires — just asking, breaking, fixing, shipping.
The honest numbers (90 days in):
~540 weekly visitors
6 active API consumers
~200 real API calls
0 paying customers
$0 revenue
The infrastructure cost me 100× more in learning curve than in money. The silence is the hard part.
Why I'm posting:
Not to sell. The free API tier is genuinely free — no card, no tricks. I'm posting because most indie SaaS stories are either day-one launches (no data) or post-success write-ups (revisionist). This is the middle — built but unsold — and I think more founders should see what that actually looks like from the inside.
If you've been here: what actually moved the needle on distribution for you? That's the wall I'm staring at now.
— Kobus, George, South Africa
1 Comment
I'd be careful treating this as a distribution problem too early.
The interesting part isn't that 540 visitors became 0 customers.
It's whether the current signals are actually pointing at a distribution issue in the first place.
That's one of those decisions that can quietly consume months if it's wrong.