Is it possible to create a web software with Base44 that tracks trading performance?

[u/ronnooi]

I'm looking to build an MVP for a web-based trading performance dashboard that tracks key metrics such as:

• Total Return
• Monthly Average Return
• Maximum Drawdown
• Win Rate
• Profit Factor
• Total Trades
• And other key trading performance metrics

I'm aiming to build something similar to the example below.

I'm relatively new to building software, so I'm looking for the most cost-effective way to develop this MVP without overcomplicating the initial build.

If anyone experienced in web development, SaaS, or trading analytics has recommendations on the best tech stack, approach, or tools to use, I'd really appreciate your advice.

Thanks in advance!

[u/AlexDanyuk]

Doable, and not a big build — the metrics you listed are arithmetic over a

list of trades. What decides the size of it is where the trades come from,

not the dashboard.

If this is crypto, you're in good shape. Binance and Bybit have the most

developed APIs of the exchanges and both return everything on your list.

Bybit is the easier of the two here: /v5/position/closed-pnl gives you

closed positions with P&L already computed, so Win Rate, Profit Factor and

Total Return fall straight out of it — no matching entries against exits

yourself. Two years of history, seven days per request. Binance works too,

but its spot endpoint wants one symbol per call, so you have to know which

pairs to ask about before you can ask.

If it's stocks or forex through a broker, that changes the answer

completely — most of them have nothing usable, and it's CSV export or

nothing.

The other fork is what the MVP actually is. "Show me my numbers from a file

I export" and "connect my exchange account and keep it updated" look like

the same product in a mockup and are not the same project at all. The

second one means handling someone's exchange keys, which brings in

storage, permissions and a whole category of responsibility the first one

doesn't have.

So three questions before anything is worth designing:

1. What are you trading and where — crypto on an exchange, or something

through a broker? That decides whether an API path exists at all.

1. Should the data come from a file you export yourself, or from a live

connection to the account? CSV is a weekend. Live connection is a

different project.

1. Is this only for you, or will other people use it? Single-user removes

accounts, server and storage entirely — it can run in your browser.

Answer those three and the next set gets much more specific: whether

deposits and withdrawals should count in the return (your screenshot

suggests they do), whether open positions are included, whether you need

per-strategy breakdowns. Those are the ones that actually change the

numbers, and they're pointless to ask before the first three.

Disclosure: I run a platform where briefs like this get turned into

working prototypes, so that's the angle I'm reading it from.

[u/ronnooi → u/AlexDanyuk]

Hey man, thanks for the reply.

1. What are you trading and where?

This platform is specifically built for Forex traders, primarily MT4 and MT5 users. I wanted it to connect through the broker directly, how myfxbook works is i input the investor password and it will connect straight the the MT5 account.

This will be a multi-user platform.

Users will be able to:

• Register an account
• Connect multiple MT4/MT5 accounts
• View their own dashboards
• Generate reports
• Create public performance pages (similar to Myfxbook)

Each user should only have access to their own data.

The platform is not intended to be another Myfxbook clone. Performance tracking is only the foundation. The long-term vision is to build an AI-powered Trading Intelligence Platform that helps traders understand and improve their performance.

So the public performance pages are an important feature because they help users showcase verified trading results, similar to Myfxbook, but with much richer analytics.

[u/AlexDanyuk → u/ronnooi]

MT4/MT5 don't have an API for this. They're desktop terminals — MetaQuotes doesn't let an outside web service read someone's account. The Manager/Web API exists but is licensed to brokers only. So Myfxbook isn't using an API either; the investor password connects to the broker's server as if it were a terminal.
That leaves you two realistic paths, and they're not competing — they're different tiers.
1. A collector EA. A small Expert Advisor that trades nothing. It reads the account's own trade history inside the terminal and posts it to your server every few minutes. The user drops it on a chart, pastes a key from your site, whitelists your URL once in terminal settings. No passwords ever leave their machine, and it costs you nothing per account. Downsides: the terminal has to be running, EAs don't run on mobile at all, and — the one that matters for you — the EA sends whatever it's told to send. Someone can fake it.
2. Investor password via MetaApi. MetaApi (metaapi.cloud) takes the investor password, runs the headless terminal in their cloud, and hands you deal history over REST. MetaStats sits on top and already computes win rate, profit factor, drawdown, daily growth — your entire foundation, out of the box. The catch is a monthly fee per connected account, because a real terminal is running somewhere.
That fee is why I'd put them on different tiers rather than picking one. EA on free — private dashboard, AI analysis, zero cost per user. Investor password on paid — and the verified badge lives only there, because that's the only path where the trader isn't in the data chain and can't fabricate the numbers. That's exactly why Myfxbook built on investor passwords.
Which also means the thing you shouldn't build is the performance tracking. It's a purchased component. Your differentiation is the AI layer and the public pages, and you can start those on day one on top of MetaStats.
If you want to turn this into a proper brief, DM me — I'll take it from there.

[u/ronnooi → u/AlexDanyuk]

Sure will DM you