For the people who ask how it is built
Most platform pages stop at a logo wall. This one is for the operations lead, the compliance officer and the diligence team who have to know how the thing is actually put together, and what is not built yet.
The platform runs as two separated systems on major public cloud infrastructure. One holds the operating book and the records: accounts, sleeves, orders, lots and performance. The other carries the advice work: risk assessment, planning, the client record and the portal. They exchange data over private, allowlisted channels rather than sharing a database, so a fault or a change on one side cannot quietly rewrite the other.
Billing runs as its own service against the operating book, through a single fee path. There is one place fees are calculated and one place invoices come from, which is the only way a fee question ever gets a single answer.
Access runs through one identity layer across every surface, with role-based permissions and entitlements scoped to a firm and its entities. Multi-factor authentication is available through the identity provider. Administrative access to infrastructure runs through private networking with address allowlists rather than open endpoints.
Traffic is encrypted in transit at every edge, and storage is encrypted at rest by the managed platforms underneath. Dependency and static code scanning run in the build pipeline, so a vulnerable library is caught before it ships rather than after.
We are not the custodian, we never hold client funds or securities, and we earn nothing from your clients’ cash. The custodian remains the legal record for positions and tax basis. Our operating book carries accounts, sleeves, working lots and performance. The advice system owns assessments, planning and the client record. Every shared figure has exactly one owner and one expression, which is why the same number does not appear two ways in two reports.
Everything above runs in production today. The following are planned, and we would rather say so than imply otherwise: an independent penetration test, a SOC 2 examination, a formal high-availability and disaster-recovery attestation, and a write-once records vault for books and records.
If your diligence team needs more than this page, we will send the full platform and technology notes, which mark every capability as live, in progress or planned, and we will answer a security questionnaire.
Questions this did not answer? Ask them directly — that is what the twenty minutes is for.
Schedule a call to see for yourself