Skip to content

Back office, risk desk and dashboards

Staff spend their day in the back office: reviewing breaches, acting on accounts, answering a trader who says a rule was applied wrongly. Traders spend theirs watching how close they are to a target or a floor.

What tends to go wrong

  • With several staff roles, permission checks written route by route leave gaps.
  • Staff actions without an audit log are hard to explain when a trader or a regulator asks.
  • A dashboard that calculates its own numbers can disagree with the engine that decides the outcome.

What I've built

NEXETRO staff tools

The admin backend and most staff screens: accounts, breaches, the risk desk and manual actions.

See it in the case study: NEXETRO staff tools

Role-based admin

On My Forex Firms, a prop-firm review platform, I moved role checks into shared guards used across the admin API, with protection against admins demoting themselves.

See it in the case study: Role-based admin

Audit log off the request path

Handlers queue audit events and a scheduled job writes them to Postgres in batches, so logging never slows down or fails a request.

See it in the case study: Audit log off the request path

What traders complain about

The same platform structures complaints against prop firms, with firm responses, moderator outcomes and a trust score. It's a close look at the disputes a firm's tooling has to answer.

See it in the case study: What traders complain about

What I can take on

  • Admin panels and staff tools with role-based access.
  • A risk desk over breaches, exposure and flagged accounts.
  • Trader dashboards that show targets, floors and payout eligibility from the engine's own numbers.
  • Audit logs for staff actions.

What I haven't done yet

I haven't integrated a third-party prop-firm CRM. If you use one, the work would be against its API, and I'd scope it that way.

Related work

  • Challenge and risk engine

    Profit targets, daily-loss and drawdown floors, consistency rules, phase progression and breach detection.

  • Trading engine and market data

    Market-data ingest, execution against real order-book depth, perpetual futures and a live trading terminal.

  • Ledger, payouts and reconciliation

    A double-entry ledger for fees, refunds and payouts, with idempotent money changes and scheduled reconciliation.

All prop firm development work

Building or fixing part of a prop firm?

Tell me which platform or market data you use, roughly how many accounts you run, and what needs to change. I'll reply with questions or a first outline of the work.

Get in touch