Securities brokerage and trading for banks

AbenAlpha

One system for a bank's securities business: retail brokerage, institutional agency and principal trading, limited proprietary trading.

Orders, pre-trade risk, positions, settlement and MiFID II records in one Rust server that the bank deploys and runs.

StatusIn development. The target architecture is designed; it builds on an existing Rust back end and web client.

At a glance

  • One deployment per bank

    Legal entities, branches, desks and books in one deployment. Nothing is shared with another bank.

  • Rules in the server

    Business rules live in the Rust core, not in the browser and not in database constraints.

  • Evidence by design

    Every change writes its audit-ledger entry in the same transaction. The ledger is hash-chained and append-only.

  • No third-party SaaS at run time

    Identity provider, venues, market data and regulatory feeds are external systems behind ports.

StatusIn development
ForBanks: brokerage and trading
DatabasePostgreSQL
Sign-in (target)Microsoft Entra ID

01 — Scope

What AbenAlpha covers

Each item says whether it exists in the current build or is part of the target design. Target items are designed and documented, not built.

  • 01

    Client categories

    Built
    Retail clients, professional clients and eligible counterparties. The category decides which checks an order must pass.

  • 02

    Order lifecycle

    Built
    Order states aligned with FIX, amendment with versions, cancellation and stop orders. Every command carries an idempotency key.

  • 03

    Order flows

    Target design
    Retail client orders, institutional agency and principal orders, and house orders of the bank's own traders, each with its own checks.

  • 04

    Pre-trade risk checks

    Target design
    A synchronous engine inside the order transaction: price collar, maximum order value and quantity, message rate, position and exposure limits.

  • 05

    Limits and kill switches

    Target design
    Limits per client, user, desk, book and branch. Kill switches at user, desk or book, client, venue and firm scope. Re-enabling needs a second person.

  • 06

    Positions, P&L, market risk

    Target design
    Positions per book, profit and loss, market-risk runs. Client books and house books are kept apart.

  • 07

    Credit and collateral

    Target design
    Credit lines, counterparty exposure, margin and collateral.

  • 08

    Venues and market data

    Partly built
    Execution venues and market data sit behind ports. A venue simulator exists for development and demonstration; a FIX gateway is the target for bank production.

  • 09

    Allocation and settlement

    Partly built
    Cash, reservations and pending settlement are kept today. The target adds allocation, settlement instructions, confirmations and fails.

  • 10

    MiFID II client records

    Built
    Versioned suitability profile, meeting minutes with suitability and appropriateness statements, and ex-ante cost disclosure documents stored with a content hash.

  • 11

    Transaction reporting and surveillance

    Target design
    A reporting module for MiFIR transaction reports. Surveillance scenarios run over the full order event store and raise alerts into a case workflow.

  • 12

    Maker-checker approvals

    Target design
    Four-eyes approval for client category changes, limit changes and overrides, kill-switch re-enable and role assignment. Maker and checker must be different users.

02 — Order path

The order path

Target design. Every step writes its audit-ledger entry in the same database transaction as the change.

03 — Deployment

Built to be run by a bank

Target design. One release artefact; the bank decides who operates it.

  • One deployment per bank

    The bank is the tenant. No database, process, key, ledger chain or backup is shared with another bank.

  • Several legal entities

    Legal entity, branch, desk and book in one deployment. Every business record carries its legal entity.

  • Bank-operated or vendor-operated

    The same signed release runs in the bank's own data centre or cloud, or on infrastructure dedicated to that bank.

  • Separate environments

    Production, pre-production and test are separate deployments with separate databases, keys and networks.

  • No internet from the servers

    A release is one bundle, verified offline against a signed manifest.

  • Two sites, one writer

    One active application node at a time and a synchronous database standby in the second site.

Clients

  1. Desktop client. A Tauri desktop application around the existing web client. It holds no business data and no business rule.

  2. Installed by the bank. A signed Windows installer, rolled out by the bank's software distribution. The bank edition never updates itself.

  3. Browser client. The browser client stays. In the bank profile, order entry is reserved to the desktop client.

  4. Hungarian and English. The interface is in Hungarian and English.

04 — Trust

Trust you can verify

Records a supervisor, an auditor and the bank's own control functions can rely on.

  • Hash-chained audit ledger

    Built

    Every command writes its ledger entries in the same transaction as the change. Corrections are new entries; nothing is updated in place.

  • Personal data sealed at rest

    Built

    Client personal data fields are sealed with a key per client. Erasure destroys that key: the fields become unreadable in the database and in the ledger, without rewriting any entry.

  • Business rules on the server

    Built

    Nothing that affects money or status is trusted from a client. The browser only displays what the server allows.

  • Sign-in with Microsoft Entra ID

    Target design

    The bank's own Entra ID tenant with multi-factor authentication. Role- and branch-based access, with a machine-checked list of incompatible roles.

  • Information barriers

    Target design

    Proprietary traders see no client identity, order or position. Wall-crossing is approved, time-boxed and logged.

  • Keys in the bank's HSM

    Target design

    Signing and key-encryption keys are held in a hardware security module through PKCS#11. If the HSM is unavailable, there is no fallback to a software key.

Where does it stand?In development. A Rust back end and a web client exist today: order lifecycle, settlement and cash, client master, instruments, positions, MiFID II records and the audit ledger. The bank-scale target is designed and documented as decision records and a staged roadmap. Items marked Target design are not built yet.

RegulationThe design maps obligations from MiFID II and MiFIR, MAR, CSDR, DORA, GDPR, anti-money-laundering rules and Hungarian law to software requirements. It is a design input, not legal advice: the deploying bank's compliance and legal functions confirm each obligation before go-live.

05 — Contact

Ask for
a briefing.

The design, the current build and the roadmap, explained for the bank's business, risk, compliance and IT teams.

Product

AbenAlpha

In development

Other products

AbenAudit · SecReg

Contact

Aben Consulting Kft.

1037 Budapest, Visszatérő köz 6.
info@aben.ch
+36 70 336 4324
www.aben.ch