Token issuance & asset tokenization
Evidence for that status: Legacy MLG engagement software. No repository in the group’s current estate; capability claims unverified pending the asset inventory (D-A).
What it does
Issuance
Instrument configuration, contract deployment and a rehearsed test issuance before the offering opens.
Transfer restriction
Jurisdiction, accreditation and lock-up rules as versioned policy, enforced on transfer.
Register
The record of holders and entitlements, with reconciliation against a transfer agent.
White-labelled, and not
Yours
- Brand, domain and the holder-facing interface
- Instrument and restriction configuration
- Disclosure and reporting templates
- The support relationship with your holders
Not white-labelled
- Securities registration and any regulatory permission to offer
- The transfer agent relationship, where one is required
- Legal opinions on the instrument
Integration surface
REST for issuance, restriction rules and register queries; webhooks on transfer and restriction events; an export the transfer agent can reconcile against.
Who operates what
The licensee owns the offering, its documents and its regulatory relationships. We own the software. Where the register and the governing documents disagree, the documents decide — the platform is built so that outcome is reachable.
- Deployment
- Your cloud · ours · hybrid
- Register
- On-chain with reconciled export
- Licensing
- Per issuance + annual
- Support
- Tiered; SLA in contract
Publication gate: capability claims on this page are verified against the running software before publication. Lineage: Built in-house. Product name, version and capability set are pending the asset inventory (D-A); nothing on this page should be treated as verified until it lands.
Reference deployment
Held back pending written client permission. No named licensee is published without it.
Request a technical evaluation
Engineers on both sides, against your requirements. If the software does not do what you need, this is where you find out.