Verifies the holder
Portal checks identity and eligibility with Veritas before any material appears.
Named engine · Application and operations layer
An investor portal with staged disclosure.
Portal is where verified holders see what they own and what the issuer has disclosed. It combines a data room with reporting, confirms identity and eligibility through Veritas before showing material, stages disclosure in a set order, and reports ownership and servicing data from Registry. Accredited checks are performed by the licensed provider, and Portal uses no return language.
What it does
Portal is the investor portal, combining a data room and reporting. It presents staged disclosure and reporting to verified, eligible holders, drawing identity from Veritas, ownership from Registry, and operating context from Stratum. Accredited checks are performed by the licensed provider, and the page uses no return or performance language.
How it works
Three steps, each with one job.
Portal checks identity and eligibility with Veritas before any material appears.
Material is released in stages, following the investor-narrative model.
Holders see the ownership and servicing data that Registry maintains.
Where it fits
Portal sits in the application and operations layer and is the holder's window onto the platform. It depends on three engines, and nothing draws on it.
An investor portal with staged disclosure.
Depends on (3)
Used by (0)
Veritas supplies identity and the accredited verification context produced by the licensed provider, so Portal knows who is looking and what they may see. Registry supplies ownership and servicing data from the register of holders, including corporate actions over the life of the asset.
Stratum supplies operating context: the roles, access, and tenant settings that decide how the portal behaves for each client.
Equilibrium lists Portal among the engines that read its model, so holder reporting can draw on the same framework the rest of the platform uses. Portal remains an endpoint: holders read it, and no engine takes input from it.
Because Portal reads rather than writes, it cannot change a holding; a change of holder happens only in Registry, under Sentinel's rules.
Standards and integrations
Controls
Portal enforces access: no material reaches a holder until Veritas confirms identity and eligibility, and disclosure follows its staged order.
Common questions
Short answers to the questions people ask most about this topic.
Verified, eligible holders. Portal confirms identity and eligibility from Veritas before presenting material.
The licensed provider performs them. Portal presents the result and stages disclosure accordingly.
Portal shows ownership and servicing data from Registry. It uses no return or performance language.
Material is released in a set order rather than all at once, aligned to the investor-narrative model.
From Registry's register of holders, the same record that servicing and the marketplace rely on.
Operating context: the roles, access, and tenant settings that decide which material each client's holders see and how the portal behaves.
Where next
The pages below pick up where this one ends. Start with the one closest to where your asset or programme stands today.
Last updated:
Insights

Since 17 September 2026 a tokenized securities venue may run automated liquidity pools in tokenized listed stock without registering as an exchange, on conditions.

The GENIUS Act binds payment stablecoin issuers from 18 January 2027, not the firms that hold or settle in stablecoins. Service providers follow in 2028.

The CLARITY Act stalled on a 49 to 50 vote, so tokenized securities stay with the Securities and Exchange Commission, as before.

Guernsey's guidance of 24 July 2026 lets a fund or issuer record and transfer its investments as tokens, under the regimes already applying to it.
Tell us what you want to tokenize.
We will show you how DAMREV can run it.