Separation of duties
Privileged actions require a maker and a separate checker. The system refuses an approval where the creator and the approver are the same person, rather than relying on staff to observe the rule.
About Milford
Built around the record, not the pitch.
We are an investment manager and investment-operations business. The distinction matters: we take responsibility not only for allocation decisions, but for the books, records and controls that prove what actually happened to your capital.
Our position
Operational integrity is the product.
Investors are rarely harmed by a thesis that did not work out. They are harmed when records are unreliable, when balances cannot be independently verified, and when nobody can reconstruct the sequence of events after the fact.
We built Milford the other way round. The ledger, the reconciliation engine and the audit chain came first. Client-facing features sit on top of that foundation rather than beside it.
The result is a platform where every balance traces to a posted journal, every journal traces to an approved business event, and every approval traces to a named actor and a timestamp.
Governance
Controls that do not depend on trust.
These are structural properties of the platform, enforced in the database rather than by policy documents alone.
Immutable posting
A posted journal cannot be edited or deleted. Corrections are made by reversal entries, so the original record and the correction both remain permanently visible.
Custody separation
Our business database holds public account and address metadata only. Private keys, seed phrases and signing credentials are deliberately outside the model and are never stored in our systems.
Fail-closed integrations
An unconfigured or unrecognised provider adapter refuses to run rather than degrading to a default. Production startup rejects development authentication and fixture modes outright.
Chained audit records
Security and privilege events are recorded in a verifiable chain, so tampering with the history is detectable rather than merely discouraged.
Segregated administration
The operations area uses its own credential channel, issued individually, with server-side session revocation and no path to self-registration.
Our team
The people accountable for your mandate.
Specialist investment, operations, compliance and client service teams support every account from onboarding through reporting.
Investment Committee
Portfolio oversightResponsible for portfolio discipline, risk review and the mandate standards applied to each investment plan.
Operations Team
Account administrationResponsible for settlement checks, reconciliation, custody coordination and day-to-day client account controls.
Compliance Team
KYC and approvalsResponsible for onboarding review, jurisdiction controls, monitoring and escalation where additional checks are required.
Client Relations
Client serviceResponsible for client enquiries, mandate reviews, documents, account support and service coordination.