About
A journal, not a dashboard
Trade Journal is a trading performance journal for crypto, forex, commodities, stocks and futures. It exists because remembering how you traded and knowing how you traded are not the same thing.
Why it exists
Most trading tools are built to help you place the next trade. Almost none are built to help you understand the last hundred. The gap between them is where accounts quietly go wrong: the setup you are sure works, the hour you keep trading badly, the size you creep into after two wins — none of that is visible from a broker statement, and none of it is visible from memory either, because memory rewrites itself around outcomes.
So this is a journal first. You log the trade, and you write down why you took it. Later, the record — not the feeling — tells you where your edge actually is.
What it does
- Every trade, in full — entries and exits as individual fills, fees split into commission and swap, screenshots, notes, a strategy and a grade.
- Statistics that mean something — R multiples, expectancy, profit factor, win and loss streaks, max drawdown, Sharpe and Sortino, performance by strategy, by hour of day, by duration.
- A daily, weekly and yearly journal — three grains of written reflection, each filterable and exportable, because a year's worth of "why" is the part that compounds.
- A strategy playbook — each strategy's real record sitting directly under your notes on how it is meant to be traded.
- Accounts and cashflow — several accounts in one journal, with deposits and withdrawals kept separate from trading P&L so the balance is never a lie.
- Exports that outlive the app — Excel, CSV, PDF, Word, and a self-contained interactive HTML report that needs nothing but a browser.
Local-first, by design
The app was built to work with no backend at all: no network calls, no account, your journal on your own machine — IndexedDB in the browser, plain JSON files in the Windows desktop app. That version still exists, and it is still what everything else is built on top of.
Accounts came later, because syncing between a desktop and a phone is a real need. But the offline path was never demoted to legacy: it is the fallback the whole cloud direction stays reversible through, and it is covered by the same tests as everything else. If the hosted service disappeared tomorrow, the app would still be an app.
The same instinct explains the smaller decisions. Fonts are bundled rather than fetched from a CDN, so a packaged app running offline looks right. There is no analytics and no tracking — see the privacy policy, which is short because there is little to say.
Who builds it
One person: Brij. This is a personal project rather than a company — no team, no funding, no roadmap deck. It is free, and it is built because it is the tool its author wanted to use.
That is worth saying plainly for two reasons. It means feature requests and bug reports go to a human being who reads them, which is the good half. It also means there is no support contract and no uptime promise behind it, which is the honest half — the terms spell that out, and the short version is: keep your own backups.
Get in touch
Bugs, ideas, or a question about how something is calculated — the contact page is the place, or email brijk06@gmail.com directly.