Development services

Trading bot dashboards and read-only reporting

One view of the balances, positions, fills and software health you now check in several places, built on read-only access to your own accounts. Every number shows its source and its age. There is no order button, and the dashboard does not tell you what to do.

Who it is for

Who needs one view of the numbers

  • Traders and companies with several accounts

    Each platform shows only its own account, so total exposure to one asset, overall P&L and the largest position take a spreadsheet to work out.

  • Finance and operations staff

    Reporting software for finance has to tie figures back to platform records at month end, with a trail someone else can follow. That takes position and balance reconciliation as well as a chart.

  • People running trading software

    A trading bot dashboard or UI answers plain questions without opening the logs: is the process alive, when did the last message arrive on each stream, how many errors were there, how much of the rate limit is in use.

  • Teams with a product of their own

    Internal status and support screens for your staff. If your customers will see the screens too, it becomes an app: see fintech app development.

Read-only

Why read-only access is the starting point

The key has read permission only. Where a platform lets software check a key's permissions, the dashboard does that at start-up and refuses any key that can do more. The code contains no order or transfer calls, so a bug or a stolen dashboard login cannot place a trade through it.

Of the software Fincode builds, this kind has the fewest legal and operational moving parts, because it places no orders and moves no funds. It is still not free of rules: platform terms apply, market data shown to other people can need a license, and a feature that tells someone what to buy changes what the product is. Check your own situation with a lawyer; this page is not legal advice.

Failure cases

How dashboards end up showing the wrong number

A chart can look right and be wrong. Each case below is handled in the design and tested on purpose.

  • A stale figure that looks live

    One platform's sync failed an hour ago and the total still looks current. Every figure carries an as-of time. Past a limit you set it is marked stale, and a total with a missing account is marked partial.

  • A transfer counted as profit or loss

    Moving funds between your own accounts looks like a withdrawal on one side and a deposit on the other. Own transfers are paired by asset, amount and time, and the network fee stays a separate row.

  • A fee charged in a third asset

    The fee on a fill is taken in a different asset, so P&L ignores it and the balance stops matching. Fees are stored as their own rows, in the asset charged.

  • Two P&L figures that disagree

    Your computed figure and the platform's can differ because of method, funding or fees. Both are shown, and the cost method is written down.

  • A missing price shown as zero

    An asset with no price source shrinks the total without warning. It is shown as having no price and left out of the total, with a note saying so.

  • A dashboard that eats your bot's rate limit

    A page that polls the exchange on every view draws on the same request limit as your trading software. A backend collector with its own request budget reads the platforms, and browsers read only from its store. API keys never reach the browser.

  • A day that starts at a different hour

    Daily P&L differs from the platform's because one day starts at midnight UTC and the other at local midnight. The reporting day and time zone are fixed in the definitions sheet.

  • Alerts nobody reads

    Repeated alerts teach people to mute the channel. Alerts are deduplicated with a cool-down, and they state facts: a failed sync, a balance gap, a threshold you set. They never prompt anyone to buy or sell.

  • A dashboard that dies quietly

    If the collector stops, the screen keeps showing the last numbers. A check from outside the system raises an alert when the dashboard itself goes silent.

Deliverables

What you receive

  • A definitions sheet: every figure, its source, formula, as-of rule and reporting currency, approved by you before coding
  • Connectors on read-only keys, with a permission check at start-up where the platform exposes one
  • A web dashboard for balances, positions, fills and software health, on your own server or cloud account by default
  • A ledger of fills, fees and transfers, with scheduled reconciliation against what each platform reports and a list of open differences
  • Alerts to Telegram, email or mobile notifications, at thresholds you set
  • CSV exports for your accountant or auditor
  • A test report covering failed syncs, stale data and restarts, and technical documentation

How we work, stage by stage

Sample

What a definitions sheet looks like

Most arguments about a dashboard are arguments about what a number means. This sheet settles them before any screen is built.

Before we quote

What is checked first

  • Whose accounts these are

    Yours or your company's. If a dashboard would show other people's accounts, say so in your brief: that is a different product with its own questions on consent, data protection and licensing, and your lawyer should see it first.

  • What each platform exposes

    Whether it offers read-only keys, whether software can check a key's permissions, and how far back fills and transfers can be read. Some platforms split this data across several endpoints with short query windows. Our guide to a crypto portfolio tracker API shows what that looks like.

  • What the numbers mean to you

    Which cost method, which reporting currency, when the day starts, and which price values your holdings. These go in the definitions sheet.

  • Who will see it

    Showing market data to anyone outside your company can need a display license, and some API agreements restrict data display or third-party use without written approval. Each platform's terms are checked before we quote.

  • Your country and the platform's terms

    For customers outside Türkiye, which platforms can be used depends on the law of your country and the platform's terms. For customers resident in Türkiye, we work with platforms on the Capital Markets Board's list that offer an API; being listed does not mean a platform is authorized.

An honest note

When you do not need us

With one account, the platform's own screens are probably enough. With a few accounts and simple totals, try a spreadsheet or a subscription portfolio tracker first; read its terms and check where it stores your keys. If your software already exports metrics, a general monitoring tool such as Grafana can show its health without custom software. For tax reports, use tax software or an adviser: a dashboard is not a filing.

Custom work makes sense when several platforms or sub-accounts are involved, when someone must be able to trace each number to its source, or when the tools you tried do not support your platform.

FAQ

Questions about trading dashboards

Can the dashboard place or cancel orders?

No. It works with read permission only and contains no order code. An emergency stop belongs in your trading software; see trading bot development.

What does a trading bot dashboard show?

What the scope defines. Usual items are process status, last heartbeat, the age of each data stream, open orders, error counts and rate-limit use, next to balances and P&L.

Can you build a UI for a trading bot I already run?

Yes, if the software can expose its status, for example through logs, a metrics endpoint or a database it writes. If it cannot, adding that output is the first work item. The screen stays read-only, so stop and start controls stay in the software itself.

Will Fincode watch the dashboard for me?

No. It is software you run, not a monitoring service from Fincode. Alerts go to you. Fincode does not watch your positions or act on them, and strategy and investment decisions are yours.

Is this portfolio data management software?

In the narrow sense, yes: it keeps holdings, fills and fees from your own accounts in one store, each with its source. It does not manage a portfolio. There is no allocation, no rebalancing prompt and no decision made for you.

Does it reconcile balances with each platform?

It can: the balance computed from your ledger is compared with what each platform reports, and a difference stays open until someone explains it. That is reporting on your own holdings, not accounting advice.

Does it produce tax reports?

No. It can export fills, fees and transfers as CSV for your accountant or tax software, but the export is not a filing and not tax advice.

How current are the numbers?

As current as each platform's streams and limits allow, which varies. Instead of a blanket claim, every figure shows its age, so you can see how old it is when you read it.

Can I show the dashboard to my clients?

Raise it in your brief. Showing data to other people can need a data license, and what you do for those clients can bring licensing duties of your own. Settle this with your lawyer before scope is agreed.

Does it work on a phone?

The dashboard is a web page, so it opens in a phone browser, and alerts can reach you on mobile. A native iPhone app is a separate scope: see fintech app development.

How is the price set?

You get a written proposal with work items, dates and cost before work starts. Fees depend on scope and effort, not on trading volume or results.

Tired of adding up platforms by hand?

Tell us which platforms you use, what you want to see, who will see it and your timeline. Fincode is a software company and does not provide investment advice, portfolio management or crypto asset services. Trades can lose money.

Send a brief