Platform

Runs where your data already is.

FinXAi is a desktop application talking to servers you operate. There is no hosted tenancy in the middle, and no copy of your order flow sitting somewhere you cannot point at.

Book a call Send a vendor questionnaire
Trader desktop
  • Flutter desktop client for Windows and macOS
  • Card workspace with pop-out windows per monitor
  • Market data decoding on background isolates, off the render thread
  • Layout and preferences stored in the user profile
  • Bloomberg BLPAPI through native bindings on the desktop
Installed on your SOE
Transport
  • WebSocket as the primary live channel
  • Request and response correlated by identifier over that channel
  • gRPC streaming for secondary feeds
  • Redis publish and subscribe carrying protobuf for cache distribution
Inside your network
Your infrastructure
  • Trading engine and order routing
  • Market data sources and the reference data store
  • Risk limit service receiving published limit sets
  • Identity, entitlements and the audit record
Your servers, your control

Deployment

What a rollout actually involves.

  1. Connectivity review

    We map your market data sources, your order path and your reference data onto the interfaces the client expects, and agree what adapts on which side.

  2. Pilot on one desk

    A handful of traders on the real feed, with limits set deliberately tight. This is where layout conventions and the column sets get decided.

  3. Entitlement load

    Entities, accounts, users, roles and groups configured to match the desk. Users can be created inactive ahead of their approved start date.

  4. Risk sign-off

    The risk manager builds the firm template, the instrument caps and the account allocations, and publishes the set to the engine.

  5. Desk by desk

    Packaged for your software distribution. Traders carry their own saved layouts between versions.

Security and control

Answers for the questionnaire.

What follows is how the product is built. We will work through your own control framework line by line, and we are happy to do that under NDA before anything else happens.

Data residency
Market data, orders, positions and reference data move between the trader's machine and your servers. The vendor operates no tenancy that holds your trading data.
Authentication
Credentials issued by your administrator, with password rules set by your organisation and self-service reset in the client.
Authorisation
Role determines which cards exist for a user. Account access is granted explicitly per user or inherited through a group. A change to either applies to a live session immediately.
Segregation of duty
Risk limits are administrator only. The trader has no path to their own caps, and the publish action is separate from editing.
Change control
Shared reference data carries the identity and timestamp of the last save, announces concurrent edits, and version checks writes so an overwrite is a decision rather than a race.
Source assurance
We keep a standing security review of the codebase with a tracked remediation log, and a defect register with the same discipline. Current state shared under NDA, including what is still open.
Logging
Client side logging runs on a dedicated isolate so diagnostics never compete with the price path, and writes to the user profile for collection.

Engineering

Built like something that has to be right.

The price path is the part that matters. Market data decoding and logging run on background isolates so the user interface thread is only ever drawing. Positions and exposure are throttled to a fixed cadence rather than repainting on every tick, which is what keeps a grid of forty instruments calm during a number.

The rest of it is ordinary good practice. A regression suite that runs on every change, an analyser that has to come back clean, a defect register where each entry gets its own branch and its own review, and a written user guide that is revised when a workflow changes rather than when someone remembers.

Next step

Send us your control framework.

If your procurement process starts with a questionnaire rather than a demo, that suits us. Send it over and we will return it completed, then book the call.

Book a call