Review
The client submits the Structuring Review, and a named person at DAMREV replies on a stated day.
Service
A client works with DAMREV in one of three ways: as a white-label client under its own brand, as an application programming interface (API) client driving the platform by integration, or as a platform user on DAMREV's own platform. Each works inside its own isolated tenant, and DAMREV carries its programme within a single mandate.
Ways of working
Three, each resting on a tenant. They differ in whose brand the client's users see and how much of the platform the client configures directly. The platform is configurable within DAMREV's tokenization framework, not a fixed product used the same way by everyone.
A white-label client takes the platform under its own brand and customises it within a scoped surface. Atelier provides visual theming for client surfaces, and Stratum carries roles and functional configuration.
The controls underneath do not change with the brand. Identity, eligibility, and transfer rules run through Veritas and Sentinel whatever name the client's users see, and credentials are aligned with the World Wide Web Consortium (W3C) Verifiable Credentials 2.0 standard1.
An API client drives the platform by integration, customising through configuration and capability endpoints. It builds on contracts that run as Soroban smart contracts on the Stellar ledger, live on mainnet since February 20242.
An API client usually has its own systems and a technical team, and connects selected engines into an existing architecture rather than taking the whole stack.
A platform user works on DAMREV's own platform, personalising within role and tenant limits. It needs no technical team and no brand work.
Rules still configure per jurisdiction and per asset, and enforcement runs through the same engines as every other way of working.
Every client, whichever way it works, has a tenant: an isolated space for that client's data and configuration.
The tenant keeps one client's programme, roles, and records apart from every other client's. DAMREV's own operations run in a tenant of their own on the same platform.
What you get
Whatever the way of working, the same four things. The brand and the depth of configuration change; the controls and the isolation do not.
How it runs
As steps in one mandate. The same mandate can run across structuring, capital formation, and tokenization, which is what most clients end up doing, with the legal and regulated functions staying with the appointed counterparties throughout.
The client submits the Structuring Review, and a named person at DAMREV replies on a stated day.
The client and DAMREV agree white label, API, or platform use, and what each party operates.
The client, counsel, and DAMREV settle the structure and design the programme.
DAMREV configures the tenant and brings the programme live with the appointed parties.
The client or DAMREV operates the programme, and servicing runs for life.
Who it suits
Issuers, managers, and firms that want a configurable programme. The format of the instrument does not change the law that governs it3, so every engagement keeps the regulated roles with the parties that hold them.
What you provide
Enough to choose the way of working. The rest follows from the Structuring Review.
01
02
03
04
05
How it is charged
On up to three bases, depending on the services in the mandate. Orchestration of the programme covers the work of reviewing, designing, structuring, and bringing it live. Servicing for the life of the instrument covers operating and servicing it once issued. Success tied to capital actually settled applies where a raise is part of the mandate.
Where it leads
Most start with the Structuring Review. The furthest step is a programme DAMREV operates for you.
Common questions
Short answers on the ways of working: which needs a technical team, whether a client takes every service, which DAMREV entity does what, what a tenant is, whether you can put your own brand on the platform, and whether you can use only some of the engines.
Only the API client, which integrates directly. A white-label client and a platform user work on the platform DAMREV operates, with no blockchain team of their own.
A client takes the programme as one mandate, from the Structuring Review through structuring and implementation to servicing, with managed operations where DAMREV runs it. Where a programme needs less, the reduced scope is agreed in writing before any work begins.
DAMREV Labs, LLC, in Wyoming, builds and operates the software. DAMREV Capital Partners, in Mauritius, is a separate entity that can act as issuer and general partner. Permissions are held entity by entity.
An isolated space for one client's programme, data, roles, and configuration, held in Stratum. Every way of working rests on one, and DAMREV's own operations run in a tenant of their own.
Yes, as a white-label client. Atelier applies your colours, marks, and type to the surfaces your users see, while the roles, permissions, and transfer rules underneath stay the same.
Yes. A client can take DAMREV as the whole programme stack, or connect selected engines into its existing architecture and keep its own permissions, systems, and operating boundaries.
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.