UNIFINplatform

Platform

One core, every market function

Trading, clearing, settlement, depository, payments, risk and data live in one governed core of 50 microservices. Every service owns its database, publishes an API and ships on its own release cycle; the platform grows by adding bricks, not by rebuilding.

  • 50 microservices
  • 9 portals
  • 126 gateway routes
  • 978 documented endpoints
  • 43 databases
  • quarterly releases since 2020
Roadmap and releases

Business map

The platform in business: one front-to-back circuit

A trade passes the whole platform: from the client workplace to the ledger entry and the regulatory report, without leaving one circuit. Twenty-seven business modules in four layers, each with its own role and its own users.

Front office
The deal is born: channels and workplaces, orders and matching, auctions, OTC deals and repo, FX, derivatives, listing and offerings, the commodity warehouse, digital assets.
Client, trader, trading operations
Middle office
The deal is checked and secured: risk and limits, clearing and the central counterparty, collateral, margin and default management, master data and the calendar, compliance and supervision.
Risk manager, clearing, compliance
Back office
The deal is settled and accounted for: DVP and FOP settlement, the central depository, payments and the bank circuit, corporate actions and tax, the financial journal, reporting, documents and confirmations.
Back office, treasury, accounting
Platform
Cross-cutting services: gateways and FIX and ISO 20022 integrations, access and roles, audit, the scheduler, administration, the sandbox.
Administrator, integration, operations

How it works

The journey of a trade: from the client cabinet to the report of the day

One trade passes all four layers with no manual hand-offs between suites.

  1. 1

    An order from the cabinet

    The client places an order; limits and checks pass before it reaches the book.

  2. 2

    Matching and the trade

    Opposite orders meet on price and time; the trade goes to clearing.

  3. 3

    Clearing and collateral

    Obligations of both sides are counted and netted; coverage is confirmed by margin and the pool.

  4. 4

    Settlement and records

    DVP moves securities against cash; the depository, the journal and the balances record the result.

  5. 5

    Reporting and supervision

    Reports of the day leave on schedule; an immutable trail remains for audit and the regulator.

Service catalogue

All 50 microservices

Seven groups cover the platform from foundations to sandboxes. Shared services (identity, audit, workflow) support every business suite; each business service keeps its own store and contract.

Foundations

  • auth identity and sessions
  • day-schedule trading calendars and phases
  • admin platform administration
  • feature-flag rollout switches per segment
  • reference-data instruments, boards, fees
  • audit immutable journal of actions
  • workflow process and approval engine

Clients and documents

  • participant participant registry and KYC states
  • participant-gw B2B channel for participants
  • signature electronic signature
  • docflow document exchange with statuses
  • training courses, exams, certificates
  • chat moderated deal chat
  • voting issuer and shareholder voting

Access and connectivity

  • server-gw API gateway, 126 routes
  • fix-gateway FIX sessions for members
  • fix-engine FIX 4.2 / 4.4 / 5.0 engine
  • esb-gateway integration hub
  • integration adapters and message formats
  • notification e-mail, SMS, push, in-app
  • ussd USSD dialogue: sessions and menus, aggregator-first
  • arbitration conflict resolution for updates

Risk and control

  • risk limits, VaR, stress scenarios
  • collateral margin and collateral
  • derivatives futures and options
  • digital-assets asset registry and custody
  • sanctions list screening
  • surveillance market monitoring and cases
  • approval four-eyes approvals

Trading and data

  • trading order book and matching
  • market-data quotes, snapshots, trades
  • listing listings and offerings
  • auction auction engine
  • indices index calculation
  • news news and publications
  • journal trade journal

Post-trade and money

  • clearing netting and obligations
  • settlement DVP, PVP, FOP
  • depository custody accounts and movements
  • payment payment orders and bank files
  • fx rates, conversions, forwards
  • ca corporate actions
  • tax withholding and tax reports

Operations and sandbox

  • reporting report engine and distribution
  • task-engine operations tasks and schedules
  • ai-agent agentic assistants
  • warehouse warehouse receipts
  • mock-bank bank simulator
  • mock-csd CSD simulator
  • mock-regulator regulator simulator

Every link between services is a contract: REST or Feign, FIX, ISO 20022 or an event with a schema version. A new brick connects without touching the core.

Technology architecture

How the platform is put together

Four layers from the portals down to the infrastructure, with the boundary and middleware in between.

Presentation Nine portals on one sign-on
Admin
Operations
CSD
Trader
Participant
Reports
Supervision
Simulation
Dev-sim
Boundary and gateway Identity, routes, participants
Keycloak SSO roles and MFA
API gateway 126 routes
Participant API gateway API keys and quotas
WAF and CSP in front of every service
Middleware and rules One integration kit
Event backbone outbox, DLQ, replay
FIX engine 4.2 / 4.4 / 5.0
ISO 20022 and MT message builders
Rules and workflow limits, approvals, fees, calendar
Business systems 50 services, own databases
Trading, clearing, settlement
CSD and custody
Payments and FX
Risk and collateral
Reference and market data
Reporting and supervision
Digital assets and derivatives
Infrastructure Observability and operations
Kubernetes + Helm
Prometheus + Grafana + Loki
Vault secrets
Backups and DR drills

Architecture scheme

The same architecture as a scheme

Layers, boundaries and links on one canvas: from portals and the access boundary to business systems and infrastructure.

Architecture scheme The same architecture as a standalone page. Open the diagram separately

Screens across the suites

Liquidity, analytics, negotiated trading, the placement book, the issuer inbox and the operations copilot.

Market depth board with quotes and orders
Liquidity board: live market depth
Analytics dashboard with platform metrics
Analytics workspace: platform metrics
OTC RFQ board with deal tickets
OTC desk: RFQ board and deal tickets
Operations copilot with a prepared decision
Operations copilot: the agent prepares, the officer decides
Placement book screen with demand and allocations
Placement book: primary market demand and allocations
Issuer corporate inbox screen
Issuer inbox: corporate workflow in one window

Build with us

What you can launch on the same core

Every product reuses the platform rails (clearing, settlement, depository, identity, audit) and adds its own store, UI and commercial model.

Market data hub

Live streams, history and files with entitlements and metering.

Own store, p95 under 500 ms

Corporate actions portal

Announce, approve, execute and pay with a full audit trail.

Weekly releases

OTC commodity trading

RFQ board, deal tickets, clearing and DVP settlement on one rail.

Money path, p95 under 100 ms

Bond platform

Placement book, secondary trading, coupon and redemption runs.

Zero-downtime releases

Index products

Published methodology, streamed values, licensing and metering.

Scales horizontally

AI analytics

Natural-language questions over live data, dashboards and a copilot.

Human in the loop

Digital assets platform

Registry with lifecycle, admission rules, screening and classic settlement.

Fail-closed admission

Derivative trading

Futures and options with SPAN margin, variation margin and cash settlement.

Launch by configuration

AI agentic layer

Agents draft and summarise; people approve; every step is audited.

Role-based data access

Your own product

Take the bricks your business needs and we assemble them into a working pilot cluster with your scenario, users and data.

Assembled in 4 to 6 weeks

Technology

Standard, open and containerised

No exotic dependencies: a team familiar with Java, PostgreSQL and Kubernetes can operate the platform from day one.

Runtime
Java 21 (LTS), Gradle 8.9
Backend
Spring Boot 3.5, Spring Cloud 2025, 50 microservices, Flyway
Portals
Next.js 16, React 19, TypeScript 5, pnpm monorepo
Data stores
PostgreSQL 17 per service (43), TimescaleDB for ticks, Redis 7 + Sentinel
Messaging
RabbitMQ 3.13 quorum queues, transactional outbox, DLQ with replay
Identity
Keycloak 26.9 (OIDC, JWT), API keys and quotas
Platform
Kubernetes + Helm, Docker Compose for pilots, HPA and rolling updates
Observability
OpenTelemetry + Jaeger, Prometheus + Grafana, Loki, burn-rate SLO alerts
Security and QA
Vault, Trivy, OWASP ZAP, 88 guard scripts, Testcontainers
CI/CD
GitLab pipelines: 74 automated checks per merge

Walk the platform with our team

One scope call: we pick the bricks for your case and show them running on the pilot stand with your data.