The five apps.

One design system, five purpose-built surfaces. Your role decides which of them you see; your tenant's entitlements decide which modules appear inside.

Compliance Console — the daily workhorse

For compliance analysts, reviewers, MLROs and permitted TrustStack operators. Observed Console surfaces include module navigation, queues, cases and read views, but tabs, SLA fields and actions vary by role, entitlement, feature flag and integration. Blocking, closing and approval require a second reviewer only where that specific workflow has maker-checker configured and verified.

Client & Onboarding Portal — white-label, self-serve

For merchant teams and their end-customers. The portal is designed to bring together onboarding, module requests, wallets, dashboards and evidence read surfaces, subject to entitlement and integration. Hosted KYC can be white-labelled where configured; domain, branding, provider disclosure, accessibility and localization must be validated for the actual deployment.

Developer Portal — FORGE, productized

For engineers: observed surfaces cover scoped show-once keys, sandbox scenarios, webhooks, limits and supporting documentation. Sandbox records are demonstrations, not proof of production behavior. Validate rule parity, event coverage, signatures, delivery logs, retries and redelivery for the selected integration before relying on them.

Evidence Portal — scoped access for auditors and regulators

The reviewed product includes role-gated Evidence Portal and grant read surfaces for authorized external reviewers. Pack visibility, timeline scope, expiry enforcement and access-event recording depend on the configured workflow and current event coverage; this is not a claim of complete regulator access or logging.

Admin Console — HELM, operationally

For permitted platform administrators: observed HELM surfaces cover tenants, entitlements, users, roles, branding, configuration and operations. Cross-tenant and support controls are configuration-dependent; verify segregation of duties and the audit events actually recorded for the intended role.