Tokeny is the Luxembourg-headquartered tokenisation platform best known as the originator of the ERC-3643 permissioned-token standard (formerly T-REX), the most-cited open standard for compliant tokenised securities on EVM rails. The platform plugs into European fund administrators, transfer agents, and asset-manager-issued tokenised vehicles, with the Luxembourg domicile placing it inside the EU regulatory perimeter that most cross-border European fund structures default to. For an institutional tokenisation operator, Tokeny is the European-perimeter analogue to Securitize in the US: a platform vendor whose differentiator is integration with the regulated wrapper rather than the on-chain protocol.
What it is
Tokeny operates as a tokenisation-platform vendor, providing on-chain issuance, transfer-agency interfaces, and compliance logic for issuers tokenising regulated securities under European frameworks. The Luxembourg base gives it proximity to the largest concentration of cross-border European fund administration (Luxembourg is the second-largest fund domicile globally after the US). The platform is a technology layer rather than a regulated entity: the regulatory perimeter sits with the issuer, the depositary, and the transfer agent.
The flagship technical contribution is ERC-3643, originally launched as T-REX. The standard is the most widely adopted open standard for compliant tokenised securities on EVM chains, designed around an on-chain identity registry, a compliance contract enforcing transfer restrictions, and a permissioned-transfer model that lets the token live on a public chain while gated to whitelisted holders. The standard is open and used beyond Tokeny's direct customer base, giving Tokeny architectural reach larger than its issuance footprint.
Operating model
Tokeny's typical engagement runs through a tokenisation issuance workflow with a regulated European issuer (asset manager, fund administrator, or securitisation vehicle). The platform handles the on-chain side: token contract deployment under ERC-3643, integration with the issuer's KYC and onboarding flow, the on-chain identity registry, and the lifecycle plumbing for primary issuance, whitelisted-address transfers, and corporate actions. The off-chain regulated wrapper (Luxembourg SCSp, UCITS feeder, AIF, or SPV) sits with the issuer and its administrator; the transfer-agent function and the legal record sit with the issuer-appointed transfer agent, with Tokeny providing the technical interfaces.
The platform is multi-chain across EVM rails (Ethereum, Polygon, Avalanche, others depending on issuer preference). The value proposition is the compliance-logic plumbing that makes a regulated tokenised security workable on a public-chain perimeter: identity registry, compliance contract, transfer restrictions enforced at the contract level.
Regulatory positioning
Tokeny operates inside the EU regulatory perimeter without itself being a regulated investment-services provider. The positioning relative to MiCA is mostly orthogonal: MiCA covers crypto-asset services and the issuance of ARTs and EMTs, while Tokeny's primary use case is tokenised securities under MiFID II, the Prospectus Regulation, and national securities frameworks. The DLT Pilot Regime is the EU framework most directly relevant for tokenised-securities trading and settlement infrastructure, and Tokeny-issued tokens have been used inside DLT Pilot Regime constructions where the issuer or venue has applied for the regime's permissions.
The Luxembourg blockchain laws (Blockchain I 2019, Blockchain II 2021, and subsequent extensions) provide the domestic legal scaffolding that allows Luxembourg-domiciled securities to be issued and recorded on DLT under Luxembourg law without falling outside the conventional securities-law perimeter. The Luxembourg base is structurally consequential: a tokenised Luxembourg fund interest under Tokeny sits inside a domestic regime that has already absorbed the DLT-recording question.
Why it matters
Three reasons. First, ERC-3643 itself. As an open permissioned-token standard, it reaches beyond Tokeny's direct customer base, and adoption by other tokenisation platforms makes it a structural data point on how compliant tokenised securities will compose on EVM rails. Second, the Luxembourg base. The concentration of European cross-border fund administration in Luxembourg gives a deeply-integrated platform a structural distribution advantage for European tokenised-fund work. Third, the platform-vendor model. Tokeny does not take regulated principal positions, which keeps the platform light on regulatory exposure and lets the issuer and administrator carry the perimeter, a cleaner separation than the integrated transfer-agent-plus-broker-dealer model Securitize runs in the US.
The competitive frame is partly conventional fund administrators with in-house tokenisation programmes, partly other European tokenisation platforms (Taurus, Obligate, SIX Digital Exchange's adjacent stack), and partly GSIB rails (Kinexys and EU-domiciled equivalents).
Open questions
- Aggregate AUM live on Tokeny's platform is not consistently disclosed; per-issuer figures circulate but no platform total.
- Whether ERC-3643 adoption beyond Tokeny's direct customer base becomes the de facto institutional standard, or whether competing standards (Securitize's Vault Registrar EIP work, others) split the field.
- Tokeny's positioning under the DLT Pilot Regime as venue and settlement-system permissions are granted.
- Interoperability with US-perimeter platforms (Securitize, Ondo's post-Oasis-Pro stack).