Tokeny

• Name: Tokeny
• URL: https://tokeny.com/
• Category: tokenization operating company / issuer-and-transfer-agent workflow operator / ERC-3643 commercialization layer
• Tags: ethereum-ecosystem
• Summary: Tokeny belongs in companies/, not only projects/, because the durable dependency is a named operator that commercializes and packages the ERC-3643 / ONCHAINID stack into issuer onboarding, investor qualification, compliance configuration, transfer-agent workflow, and lifecycle APIs. The useful question is not just what permissioned-token standard exists? but which company decides how institutions actually issue, qualify investors, configure policy, and run day-to-day tokenized-asset operations around that standard?
• What it does:
  • Sells infrastructure for institutions issuing, managing, and distributing tokenized securities and other real-world assets across blockchain networks
  • Created the ERC-3643 permissioned-token standard, then keeps operating the thicker commercial shell around it through Tokeny docs, T-REX platform workflow, and T-REX Engine APIs
  • Packages a white-label operating stack for issuers, agents, distributors, and investors, including issuance, compliance configuration, order handling, redemptions, transfers, and cap-table style lifecycle operations
  • Exposes APIs for tokenization, distribution, catalog access, identity qualification, wallet management, and related token-lifecycle workflows
  • Turns compliance into a first-class product surface via ONCHAINID-linked identity and modular compliance rules rather than leaving policy as a detached add-on
  • Publishes network-support and interoperability guidance that shows institutions inherit Tokeny-managed compatibility and operating assumptions even when the lower token standard is nominally open
• Key claims:
  • The homepage calls Tokeny “The Leading Onchain Finance Operating System” and says it created the ERC-3643 standard for compliant tokenization in 2018
  • Tokeny says it has tokenized $32 billion across 120+ successful use cases, which reinforces that counterparties are buying into a production operating shell, not only a standard
  • The docs describe T-REX Platform as a turnkey white-label platform for digital-asset marketplaces, issuers, agents, and investors
  • The T-REX Engine API materials show that integrators depend on Tokeny-managed workflows and data models for tokenization, distribution, identity qualification, and wallet/lifecycle management
  • The ERC-3643 docs describe an open-source permissioned-token protocol, but Tokeny remains the branded commercial wrapper around deployment, integration, and day-to-day operator workflow
  • The compliance docs show that policy composition sits in practical modules and identity wiring that institutions must actually configure and run, which is where the company boundary matters more than the standard alone
• Whitepaper: Tokeny’s official docs link to the T-REX v4 / ERC-3643 security-tokens whitepaper, saved locally as ../whitepapers/tokeny-erc-3643-whitepaper.pdf. The broader current source of truth for the company boundary is the Tokeny docs portal plus ERC-3643 association/docs materials; see ../whitepapers/tokeny-primary-sources-2026-04-26.md.
• Sources:
  • https://tokeny.com/
  • https://docs.tokeny.com/docs/what-is-onchain-finance
  • https://docs.tokeny.com/docs/t-rex-platform
  • https://docs.tokeny.com/docs/the-erc-3643-token-standard
  • https://docs.tokeny.com/docs/built-in-compliance-framework
  • https://docs.tokeny.com/docs/getting-started-with-t-rex-engine-apis
  • https://docs.tokeny.com/docs/what-networks-do-we-support
  • https://docs.tokeny.com/docs/ecosystem-interoperability
  • https://erc3643.org/
  • https://docs.erc3643.org/
  • https://assets-global.website-files.com/63d7968e79bf1252d92c981f/64c0f2c72ea4fb62e1c838e6_Whitepaper%20-%20T-REX%20v4%20-%20Security%20tokens.pdf

Internal linkages

• Project-layer alias: tokeny.
• Keep the protocol stack explicit: erc-3643 and onchainid.
• Useful company-layer comparisons live with archax, dinari, and securitize.

Protocol / company boundary

• ERC-3643 is the standard / mechanism layer and should stay in references/standards/.
• ONCHAINID is the adjacent identity / credentialing project layer.
• This note is the company boundary: Tokeny packages those pieces into the issuer, distributor, transfer-agent, and investor workflow that institutions actually adopt.
• That split matters because the sticky dependency is not merely a token interface. It is the named operator that decides how identity issuers, claim setup, compliance modules, workflow APIs, and supported rollout patterns get assembled in production.

Control surface

• Practical authority sits in issuer onboarding, identity-provider and claim-issuer setup, compliance-module configuration, transfer-agent permissions, API workflow design, and the operational lifecycle institutions adopt as their daily tokenization surface.

• Read Tokeny as the operating company around the ERC-3643 stack, not as the standard itself.

• Last reviewed: 2026-08-07 UTC