Built by a trader.
For traders.

Why GridTrade exists

I tried multiple journals. All of them solved „log my trades" — and stopped. None tracked the thing that was actually killing my P&L: emotions. The third revenge-trade of the day. The FOMO entry after watching the move go without me. The hand-managed stop that turned a small loss into a big one.

I started tracking that in Excel — emotion 1–5 per trade, plus a „mistakes" tag. Three weeks in, the pattern was undeniable: 80% of my losses came from 20% of my trades, and those 20% were ALL high-emotion. The Excel got too messy. I built a React version. That became GridTrade.

How I work

• · Bug-Reports get fixed within 24–48h. My co-tester Luca files Linear issues, I deploy within a day. No JIRA-ceremony, no sprint planning.
• · No VC, no roadmap committee. €24.99/month subscription is the only revenue. Decisions are made by „would this help my own trading?"
• · Built in public. Source structure on GitHub. Deploys tracked in commits. Linear board mostly open.
• · EU hosting, no US data transfer. Hetzner Frankfurt + Supabase EU. Row-level security per user. Nobody, including me, can read your trades.

The trading stack

For transparency: I trade NQ + MNQ on Apex Trader Funding. ~3 trades per day, NY-Open window (15:30–17:00 CET). Setup playbook of 4 documented patterns. 0.5% risk per trade. 1.5–2R targets. Daily review with the GridTrade calendar. Weekly review with the filters.

Not impressive. Just consistent. That's the point.

Guides I've written

Practical articles built from my own trading + journaling workflow: