Technology
A modular stack, assembled to your perimeter.
Four modules that ship together or alone: onboarding and qualification, register and transfer control, distribution and disclosure, reporting and audit. Everything else is integration.
Talk to an engineerPlatform modules
The four modules
Each module solves a problem a licensed institution cannot solve with a generic Web3 toolkit, and each is designed to produce evidence as a by-product of normal operation.
Onboarding & qualification
Investor intake, professional-investor attestation capture with evidence retention, KYC and AML vendor integration, and sanctions screening. Reliance is only ever as good as the evidence file behind it.
Register & transfer control
Holder register, wallet whitelisting, transfer restrictions, lock-ups and jurisdiction blocks — the offering's legal perimeter enforced in code rather than in a procedure document.
Distribution & disclosure
Gated delivery of offering material, versioned documents and audit-trailed content, in English, 繁體中文 and ภาษาไทย. Every change to a disclosure must be provable after the fact.
Reporting & audit
Immutable audit log, regulator-ready exports, reconciliation reports and record-access tooling. This module is the reason a licensed firm engages a vendor at all.
Interoperability layer
One interface, many rails
The integration layer normalises chains, registries and custodians behind a single contract, so your systems are written once and keep working as the landscape moves.
- Chain abstraction
- EVM networks are addressed through one interface. Adding a network is a configuration change, not a migration project for every downstream consumer.
- Registry and custodian adapters
- Certificate registries, custodians and validators plug into the same issuance and retirement pipeline, keeping the off-chain record and the on-chain record in step by construction.
- Institutional integration
- REST APIs, signed webhooks and scheduled exports designed for core banking, treasury and reporting systems, with reconciliation built for people who have to close a book.
Security & control
Least privilege, all the way down
The security model exists to make one sentence true: the client controls the environment, the register and the money path. Everything below follows from that.
- Client-owned tenancy
- Deployments run in your cloud account, on your domain, under your credentials. No client production sits inside Trilumi infrastructure.
- Time-boxed support access
- Support access is granted for a window, logged for the duration and revoked at the end. There is no standing administrative account for us to lose.
- No custody of keys or funds
- We do not hold signing keys, treasury addresses or payment accounts on your behalf. Key management sits with you or your appointed custodian.
Engineering standards
The non-negotiables
- sites ship as pre-rendered files — fast to load, cheap to serve, simple to audit
- Static-first
- sites ship as pre-rendered files — fast to load, cheap to serve, simple to audit
- contrast and keyboard access held as a build requirement, not a later fix
- WCAG AA
- contrast and keyboard access held as a build requirement, not a later fix
- English, 繁體中文 and ภาษาไทย delivered as first-class, not machine-translated
- Trilingual
- English, 繁體中文 and ภาษาไทย delivered as first-class, not machine-translated
- every deployment built from version control and re-creatable from source
- Reproducible
- every deployment built from version control and re-creatable from source
Delivery
How a platform gets built
Short cycles, working software, and a handover that is planned from the first week rather than negotiated in the last.
Controls and data model
Register, restrictions, evidence and audit schema are designed first — the parts that are expensive to retrofit and the parts a reviewer tests hardest.
Issuance and settlement
Contracts and services are built against your chosen networks, with collateral and transfer rules encoded and their parameters documented for holders.
Interfaces and disclosure
Investor-facing and operations-facing interfaces are built on the same audited data, in every language your market needs.
Handover and support
Source, infrastructure definitions, runbooks and audit exports are transferred to your team, with a support agreement that keeps access revocable.
Technical questions
Detail, for the people who will run it
Is the platform custodial?
No. Trilumi does not hold signing keys, treasury addresses or client funds. Key management sits with the client or an appointed custodian, and the platform is built so that our lack of custody is verifiable in the architecture rather than asserted in a contract.
What does the audit log actually record?
Every state change that matters to a supervisor: issuance, transfer, restriction changes, qualification decisions, disclosure versions and administrative actions — each with actor, timestamp and prior value, and each exportable in the format a regulator requests.
Can we take the code in-house?
Yes, and that is the intended end state. Source, infrastructure definitions and runbooks transfer to you. Our continuing role is support under access you grant and can withdraw.
How do you handle multiple languages?
Content is structured and translated as a first-class part of the build, not passed through machine translation at render time. We have shipped English, 繁體中文 and ภาษาไทย to production on the same codebase.
Technical briefing
Bring your architects to the first call
We would rather answer hard questions about custody, audit and failure modes early than discover the mismatch during your due diligence.