Institutional risk,
in one clear view.
Your engine's numbers, in a portal your risk committee can actually read.
The demonstration shows three views of the Meridian platform: a firm overview with $2.33bn across three client books, an interactive scenario builder applying a 2022 rate shock, and performance attribution split between allocation and selection. It also shows the engine contract switching from v1.0 to v2.0 without the dashboard changing.
Your engine already computes the risk. It arrives as a nightly file, gets pasted into a deck, and by the time the committee meets on Monday nobody can say which numbers moved or why.
Architecture
Your engine stays the source of truth.
Your payload arrives in whatever shape it already has. The adapter maps it to one internal model. Dashboards read only that.
The contract
A version bump should be a Tuesday, not a project.
Watch the payload shape change. The model beside it does not.
portfolio_idstringpositions[]arraymv_usdnumbervar_1dnumberrisk.var.horizonDaysnot in v1.0
bookBookpositionsPosition[]marketValueMoneyvar1dBasis
Everything a risk committee opens on a Monday.
Controls
Built to pass institutional diligence.
Every ingest, refresh and role change is recorded immutably.
- Role-based access
- Only the books a role permits
- Encrypted in transit & at rest
- TLS, isolated tenant data
- SOC 2-ready controls
- Least privilege, change logging
One platform, every kind of book.
- Family offices
- Multi-asset books, bespoke mandates.
- Pensions
- Liability-aware credit and rates.
- Endowments
- Macro overlays across long horizons.
- RIAs
- Client-ready reporting, no analytics team.
See your risk on one platform.
The demo opens on a populated firm — three books, 51 positions, normalized from an engine contract.
Meridian is a demonstration platform. Every book, client and figure in it is generated.