The problem
People who trade odds on betting exchanges usually watch prices on the operator’s own screens. Those screens show the order book, but they say little about how a price is moving, and nothing about the trader’s own discipline. Beginners in particular have no single place where market data, risk limits and honest information about the risks of gambling sit side by side.
What I built
I built TrendBetting, a web terminal for analysis, odds monitoring and training in exchange trading. It is not a betting site: it takes no bets, handles no money, and the current version runs on simulated demo data.
- Dashboard — bankroll indicators, a 90-day equity curve, live alerts on price movements, exposure by sport and a session discipline panel (average stake against bankroll, trades against the daily maximum, daily stop-loss).
- Odds scanner — a table of market movements with sparkline, 15-minute change, volume and a signal label (steam, drift, reversal), filtered by sport and by time window.
- Event sheet and charts — price chart, back and lay book depth, comparison of the three outcomes of a match, volatility and volume.
- Bankroll manager — a fixed-risk stake calculator that shows the suggested stake and the maximum loss before entering a trade.
- Trading journal — every trade with entry, exit, P&L and the trader’s emotional state, from “lucid” to “tilt”, so patterns become visible.
- Risk education — short modules on how an exchange works, the 2% rule and stop-loss, tilt and emotional bias, warning signs of gambling addiction, long-term bankroll management and honest backtesting, plus support contacts.
How it performs
- 7 sections, each one reachable with a keyboard shortcut from 1 to 7.
- 0 runtime dependencies besides Next.js and React: every chart is drawn in SVG by my own components.
Built with
Next.js 15 with the App Router, React 19 and TypeScript. Styling uses Tailwind CSS with design tokens in CSS variables, with a dark theme and a light theme prepared. The app can run on a Node server or be exported as static files for ordinary shared hosting.
Why it was done this way
I kept the data layer in one place. Every screen reads from a single typed module, so connecting a real exchange feed, over REST or WebSocket, means replacing one import while the data types stay the same. Writing the charts myself, instead of adding a chart library, kept the terminal light and made the static export possible.
