Post-Trade Architecture & Deployment: Cloud, Hybrid or On-Premise

Cloud · Private cloud · Hybrid · On-premise

Run it your way.
Not the vendor’s.

Where your post-trade platform runs is a board decision, not a vendor constraint. NOVA CMX is cloud-agnostic by design: the same platform, the same release train, deployed as managed SaaS, in your private cloud, or entirely inside your own data centre. Underneath it sits an n-tier architecture with a dedicated security tier – so scale, control and jurisdiction stay yours to set.

What the topology decision is worth

99.99%

cloud uptime SLA on managed deployments

NOVA CMX platform SLA

20–40%

lower total cost of ownership on cloud or managed services

NOVA production benchmarks

12 weeks

recent Tier-1 go-lives, with 70% of functionality out of the box

NOVA CLIENT GO-LIVE RECORDS

0

proprietary tiers - every layer is built on industry-standard primitives, so there is no lock-in to unwind later

NOVA technology stack

Your deployment, your call

Three ways to run it.
One platform underneath.

Pick the model your regulator, your CISO and your CFO can all sign. Change it later without re-implementing.

01 · Managed cloud

Fastest path to live

We run the infrastructure; you run the business. Rapid provisioning, predictable OPEX, no capacity planning and no hardware refresh cycle. Hosted on AWS or the provider you already use.

02 · Private cloud

Dedicated and sovereign

Dedicated infrastructure in the jurisdiction you nominate, with data residency and network controls under your governance. Cloud economics without shared tenancy.

03 · Hybrid & on-premise

Your policy, our platform

Run the whole platform inside your data centre, or split it - sensitive data local, elastic workloads in cloud. Container-native, so the topology follows your policy rather than dictating it.

Architecture

Six tiers. Each one replaceable, none of them proprietary.

An n-tier design separates what users see, what the business rules do, how the platform talks to the market, and where data rests; each tier addressing only the one beneath it. Nothing in the browser can reach the database. Every tier scales, patches and fails independently of the others.

Presentation

Web UI, multi-platform

Angular · Bootstrap

One interface, desk to branch

No fat client to distribute

Business logic

Configurable rules engine

Java · C++ · multi-process

Change rules, not releases

Configuration, not code

Integration

Standards-based messaging

REST · FIX · SWIFT · ISO 20022 · MQ

New venue, no core change

Adapters at the edge

Data

Multi-tier, warehouse-ready

Oracle · Linux · DWH-ready

Reporting never competes with settlement

Read paths kept separate

Deployment

Container-native, cloud-agnostic

Docker · Kubernetes · any cloud

Scale the tier under pressure

Not the whole platform

Security

Dedicated security tier

Keycloak · Kerberos · IdP federation · CyberArk

Identity and secrets, centrally held

Enforced across every tier

Security tier · Encryption

Security is a tier, not a setting.

Identity

Federated to your IDP - your joiners, movers and leavers process governs platform access.

Encryption

Encrypted at rest for data and backups, with keys held in your own key management where policy requires.

Containment

Segmented tiers - the presentation tier has no route to the data tier, so a web-facing compromise stops there.

Role-based entitlements down to function and field, with maker-checker on sensitive actions.

Keys stay on your side in private-cloud and on-premise deployments - we operate the platform, not your secrets.

Auditable by design, with a retained record of who changed what, in which tier and when.

Privileged access vaulted, so no standing administrative credentials sit in the platform.

Encrypted in transit across every tier boundary and every market interface.

SOC 2 Type 2 controls and standards-based interfaces your assurance team can test independently.

Identity

Federated to your IdP - your joiners, movers and leavers process governs platform access.

Role-based entitlements down to function and field, with maker-checker on sensitive actions.

Privileged access vaulted, so no standing administrative credentials sit in the platform.

Encryption

Encrypted at rest for data and backups, with keys held in your own key management where policy requires.

Keys stay on your side in private-cloud and on-premise deployments - we operate the platform, not your secrets.

Encrypted in transit across every tier boundary and every market interface.

Containment

Segmented tiers - the presentation tier has no route to the data tier, so a web-facing compromise stops there.

Auditable by design, with a retained record of who changed what, in which tier and when.

SOC 2 Type 2 controls and standards-based interfaces your assurance team can test independently.

Every hour you add to the trading week is either an hour of automation or an hour of headcount. Only one of them scales.
What it means for you

The architecture shows up on the P&L.

01

No lock-in to unwind

Standard primitives at every tier. Your next platform decision stays a choice.

02

Capacity bought where needed

Scale the tier under load instead of over-provisioning the whole estate for peak volume.

03

Regulator-ready by topology

Residency, sovereignty and outsourcing questions are answered by where it runs, not by exception.

04

Change without a release cycle

Business rules live in configuration, so operations move at market speed and IT keeps control.

05

Smaller blast radius

Tier separation and a dedicated security layer contain incidents instead of propagating them.

Capital markets - engineered

Bring your architecture standards.

We will map NOVA CMX onto your hosting policy, identity model and residency requirements – and show your IT and risk teams exactly which tier sits where before anything is committed.

Stay ahead of what's next

Sign up for our monthly newsletter for insights, trends and updates shaping the future of post-trade and capital markets.
You can unsubscribe any time.