From TradingView alerts to a strategy journal
How Quantarya treats TradingView as a signal source while keeping strategy IDs, trade lifecycle events, and execution metadata traceable.
TradingView as the signal source
TradingView is very good at producing alerts, so Quantarya does not try to replace that part first.
Instead, it treats TradingView as one signal source that can send structured payloads into a strategy.
That lets the strategy dashboard focus on what happens after the alert: trade creation, lifecycle events, filters, audit state, and performance review.
Strategy ID routing keeps it sane
Every external signal needs a destination. In Quantarya, that destination is the strategy ID.
The strategy ID gives webhooks and API clients a stable route while the user-facing metadata can change over time.
That means a title can be improved, tags can be cleaned up, and an organization can be adjusted without breaking the webhook that sends trades into the journal.
Lifecycle events are the story
An entry is only the first sentence of a trade. TP events, stop-loss events, manual closes, and edits explain the rest of the story.
Quantarya stores those events so the dashboard can separate open trades, closed trades, deleted audit rows, and lifecycle changes.
That is what turns alerts into a journal instead of a notification archive.
Christian Weiss
Christian has worked in software engineering, data platforms, and cloud infrastructure for over a decade. He currently works on large-scale AWS-based data platforms and writes about Agile delivery, estimation, planning, software engineering practices, trading systems, and the lessons learned while building Quantarya. He is also a hobby quant and the founder of Quantarya.