Why there is no table here
We sell one of these. Any feature grid we publish will have our column full of ticks and everyone else's full of crosses, because that is what those grids are for. You already know to distrust them, and we would rather not spend your attention proving it.
The reason is not only modesty. Feature tables go stale within weeks — a competitor ships the thing your table says they lack, and the page keeps claiming it for months. If you want the reasoning behind that in more detail, it is on why we do not publish a comparison table.
What follows is the checklist we would use if we were buying one. It works on any journal, including this one.
Questions about what the tool can actually see
These separate what a journal computes from what it can only have inferred.
"Where does this number come from — my file, or an estimate?" Ask specifically about slippage. No exported statement contains the price you requested, so any journal reporting slippage from an upload is estimating. See what your statement hides.
"Is the P&L gross or net, and how do you know?" Broker exports disagree, and they disagree silently. A tool that cannot say which convention your file uses is guessing on every trade. See net P&L.
"What does the trade count mean?" For stock and crypto exports, a journal that reports one row per fill rather than per round trip will show double or triple your real trade count — and every per-trade average will be wrong with it. See why ledgers need matching.
"Can it tell me I moved a stop?" Nothing reading a closed statement can. Any journal claiming to measure plan adherence from an import is measuring whether the final stop matched the exit, which is a different sentence.
Questions about your data
"Can I get my data out, in full, without asking anyone?" The answer should be a format and a button, not a support process.
"What happens to my data if I stop paying?" Read-only access, deletion after a period, or immediate lockout — all three exist in this market.
"Is my trade history used to train anything?" Worth asking explicitly. A yes is not automatically disqualifying, but it should be stated rather than discovered.
Questions about the work it costs you
"How long does one trade take to record?" Multiply by your trade count. Four minutes per trade at ten trades a day is a second job, and it is the single most common reason journals are abandoned — see keeping a trading journal.
"What still has to be typed after an import?" The honest answer is your intent and nothing else. If the answer includes prices and times, the import is not doing its job.
Where we answer badly
To keep this list honest, our own weak answers:
Broker API integration — we read files and connect to MetaTrader; several competitors have direct API links to more brokers.
Backtesting — we do not have it and are not building it. If testing strategies in one place matters to you, we are the wrong tool.
Age — some of these products have been running for a decade and have the stability that comes with it.
Marketplace and community features — shared setups, leaderboards, coaching integrations. Not ours.
If any of those are what you need, the rest of this section will not change your mind, and it should not.
What to do with the answers
Run the questions past two or three tools including us, and notice which ones answer with a mechanism rather than an adjective. "Advanced AI analytics" is not an answer; "we compute it from these columns and here is what happens when they are missing" is.
That distinction predicts, better than any feature grid, whether the numbers you get back will be worth acting on.