Portfolios, assets and financial insight for high-net-worth clients, delivered through a web application that cannot afford to be wrong. The client, the figures and the architecture stay under NDA. This log is stamped, not opened.
DisclosureStamp 3 of 3 · closed
Redacted
Said · sector, role, shape, lessons Not said · client, figures, vendors, specifics
Fig. 5 · The shape of the system · Redacted where it has to be
01
The problem
High-net-worth clients at needed to manage portfolios, assets and financial insight through a modern web application. In this sector a wrong number is not a bug, it is a liability, and a slow screen is read as an untrustworthy one.
02
The constraints
Every change audited. Integrations with that could not be changed. Performance budgets set by people who look at the same screen a hundred times a day. A regulatory frame I will describe only as .
03
What I owned
Security-sensitive, performance-driven work on the client application and the API behind it, in React, NestJS and TypeScript: , plus the integrations that fed them. The shape is in Fig. 5. The details are not.