Skip to content
DAMREV
Start a Structuring Review

Named engine · Application and operations layer

Stratum

The operating core.

Stratum is the operating core the rest of the platform stands on. It holds roles, permissions, and operating context for DAMREV and every tenant, doubles as the customer relationship management (CRM) system, and feeds that context to the other engines so behaviour stays consistent. DAMREV runs its own operations on Stratum first, as tenant zero.

What it does

What does Stratum do?

Stratum is the operating core and CRM engine of the DAMREV platform. It holds roles, access, and operating context and supplies them to every other engine. It is the first engine to carry the platform's programmability and records lifecycle, and it serves as tenant zero for DAMREV's own operations.

  • Roles and accessOne place defines who can do what, across every tenant.
  • Tenant isolationEach client's data and configuration sit in a tenant of their own.
  • Records lifecycleRecords move through their lifecycle in the same core that holds roles.

How it works

How does Stratum work, step by step?

Three steps, each with one job.

  1. Step one

    Holds roles and access

    Stratum maintains roles, permissions, and operating context for the platform and each tenant.

  2. Step two

    Feeds every engine

    Other engines read roles and access from Stratum, keeping behaviour consistent across the stack.

  3. Step three

    Runs as tenant zero

    DAMREV operates on Stratum before partners join the same core.

Where it fits

Which engines does Stratum depend on, and which use it?

Stratum sits in the application and operations layer, beneath the surfaces clients see. It depends on one engine and supplies several.

Veritas supplies identity. Stratum reads verified identity from Veritas rather than holding its own, and attaches roles and access to it. Because roles sit in one place, a permission changed in Stratum changes how every engine treats that role.

Praxis takes roles and context from Stratum, so every agent acts within a defined role. Portal takes operating context to decide how the investor portal behaves for each client, and Registry takes it for servicing. Atelier builds its visual theming on the functional configuration Stratum holds, and Reserve reports the treasury into Stratum for operations.

Standards and integrations

Which standards and networks does Stratum work with?

  • Tenancy modelEach client works in a tenant, an isolated space for its data and configuration. White-label clients, API clients, and platform users all run on this one core, each within its own limits.
  • AngularThe current generation of the platform is built with Angular, a web application framework, stated here as the engine's technical base.

Controls

What does Stratum enforce, and what does it never do?

Stratum enforces

Stratum enforces roles and access: every engine that reads from it applies the same definition of who may do what within a tenant.

Stratum never

  • Enforces transfer rules, which belong to Sentinel
  • Performs identity checks, which come through Veritas
  • Carries a token or custody function

Common questions

What do people ask about Stratum?

Short answers on Stratum: what it does, whether it is customer-facing, how it relates to Praxis, what tenant zero means, how clients are kept apart, and which clients it serves.

What does Stratum do?

Stratum is the operating core: it holds roles, access, and operating context and feeds them to the other engines.

Is Stratum customer-facing?

Stratum is the operating layer behind the platform. Holders use Portal and Vault, which draw on Stratum's context.

How does Stratum relate to Praxis?

Praxis composes platform actions through the roles and context that Stratum holds.

What does tenant zero mean?

DAMREV runs its own operations on Stratum first, before partners are onboarded onto the same core.

How are clients kept apart?

Each client has a tenant, an isolated space for its data and configuration, managed within Stratum.

Which clients does Stratum serve?

White-label clients, API clients, and platform users, each working within a tenant on the same core.

Last updated:

Ready to build on programmable infrastructure?

Tell us what you want to tokenize. We will show you how DAMREV can run it.