Broker Platform
The Broker Platform represents the broker-facing business domain used by issuers, investors, and broker operators. It provides business applications for onboarding, company management, bond issuance, investment operations, notifications, and user identity management while consuming the shared services exposed by DEUSS Core.
The current implementation (the Whitelabel Broker Platform) serves as the reference implementation for broker integrations. It demonstrates the recommended architecture, service decomposition, identity model, and integration patterns for broker applications.
Design Principles
The Broker Platform is intentionally designed to support multiple independent broker implementations operating in parallel:
- Each broker deployment is operationally independent.
- Broker platforms may be hosted on-premise or in a preferred cloud environment.
- All broker platforms share the common exchange infrastructure provided by DEUSS Core and the EBSI blockchain.
- Broker platforms are scalable stateless Kubernetes applications supporting horizontal scaling, multi-data-center deployment, and traffic distribution.
Services
| Service | Description |
|---|---|
| User Service | User profiles, identity management, passkey support, and Keycloak integration. |
| Company Service | Company lifecycle, issuer information, and company-related business operations. |
| Payment Service | Broker-side payment initiation and status presentation integrated with DEUSS Core Payment Service. |
| Notification Service | End-user notifications: onboarding updates, bond lifecycle events, and operational messages. |
| Media Service | Media asset management, image processing, and S3-backed storage. |
| Bond Issuance Service | Bond lifecycle management, issuance workflows, publication, and investment operations. |
Validator Application
The Broker Platform also includes a separate Validator Application focused on validation, compliance-supporting workflows, and validator-side backoffice operations. Its main responsibilities include:
- Backoffice-facing validation workflows
- KYC / AML related operational support
- Controlled handling of sensitive validation artifacts
- Validator-side administration and review
The Validator Application owns its own relational schema and S3-compatible document storage. Sensitive validator data remains isolated from the Broker Platform except through explicit service interfaces.