An engine under tests does the maths
The same trades give the same numbers every time you open them. The model is kept out of the maths: that rule lives in the code, not on a landing page.
Records without a review give you nothing. Analytics shows which setup, hour or instrument carries the month and which one pays for it.

A typical dashboard shows a curve and asks you to trust it. Where the number came from, which trades went in, what happens without one outlier, it doesn't say. A metric you can't take apart is no better than an opinion.
the engine counts, not the picture
How it works here
The same trades give the same numbers every time you open them. The model is kept out of the maths: that rule lives in the code, not on a landing page.
Instrument, weekday, hour, session, setup, direction, tag, month, mistake, timeframe, duration, size. Any metric can be cut by any of them.
69 widgets in coloured folders, ready boards for common questions, and metrics you describe in words. The board shows only what you need.
The builder works like a Figma frame: drag a widget from the library, move and resize frames, and neighbours make room. A new widget takes the free space, and a resized frame snaps to its neighbours' height.

Describe the metric in words: 'average R after 3 pm on Fridays by setup'. The model turns the phrase into a spec built from vetted fields, the engine computes it, and you see the result before saving. Without the model, you build the same metric by hand.

Clicking a metric opens its formula and the trades behind it. That lets you argue with a number without seeing our code.

Session, setup, direction, instrument, weekday, market regime. A cut answers which part of your trading pays for the rest.

Risk per trade, trades per day, holding time and entry hour come from your own history. The day is compared with your norm, not a textbook.

Where it differs
Some competitors have more charts. But a wall of charts leaves you to work out what to ask. Here every number opens to its formula and its trades, and you can phrase your own metric in a plain sentence.
Check it yourself
Click any metric. Its formula opens with the list of trades behind it. If you disagree with one link, the number is wrong, and that is why the chain is shown.
The order
While the trades are few, the screen says so instead of showing a confident zero.
Take a ready board or build one from the library. Describe your own metric in words.
The formula and the trades under it. If you don't like the finding, you can see what it's made of.
What it does not do
Questions
You don't have to fix formulas after every change. A pivot table breaks quietly: a formula shifts a row, and the month is wrong but looks right. Here the engine is under tests, and a mismatch breaks the build.
No. The engine computes; the model gets finished numbers and explains them. Even a custom metric from a phrase is a spec of vetted fields that the engine computes.
The screen will say the sample is small and show no finding. A zero in place of a measurement looks like a measurement, and there wasn't one.
Check the formula. Usually it's how costs are counted or when a trade is considered closed. We show our method in full so the question can be settled.
It opens to its formula and its trades. Arguing with an opaque dashboard gets you nowhere.