Tokenistry
Talk to us

Products

Tokenization Engine Transaction Engine Eligibility Engine Ownership Engine Indexing Engine Custody Integration Backoffice

Work with us

For advisers For issuers For institutions Engagement & support Specialist engineering Questions

By market

UK authorised funds Swiss ledger-based securities

Technology

Technology ERC-7943 Architecture Quickstart

Developers

Documentation API reference Demo console GitHub Docker Hub Live demo Talk to us

Tokenistry Core · Tokenization infrastructure

Blockchain infrastructure for tokenized securities. From issuance to redemption.

The token, the rules for who may hold it, and the register of who does.

Talk to us Run the live demo

Advising a client? For advisers.
Issuing an instrument? For issuers. Running it yourself? For institutions.

Designed by engineers who ran regulated production infrastructure at €1B+ scale.

What Tokenistry does

One layer sits under every tokenized security: a token that enforces its own rules, a signing path that reaches the chain reliably, and a register that survives an audit.

None of it differentiates anyone's product. All of it has to be right. Tokenistry built it once and runs it, so it is not rebuilt per issuer, per asset class or per institution.

Built for

  • law firms & advisers
  • issuing houses
  • issuance platforms
  • banks & securities firms
  • asset managers & funds
  • private-markets platforms

Bring us the mandate

For advisers

Your client asks whether their bond, fund or participation can be tokenized. You need an answer in that meeting, not after a search.

Bring us the mandate. We do the technical execution and nothing else: no advice, no placement, and no contact with your client that you did not arrange.

The instrument does not depend on us. The contracts are on chain and your client holds the key. For advisers

Operated for you

For issuers

You are placing an instrument, not building a technology function.

We operate the infrastructure behind the issuance. You hold the authority key, so nothing we run can move an investor's position. You get a register you can put in front of an auditor and export whenever you want.

The second issuance costs a configuration, not another project.

Not every issuer wants to build on an API. A backoffice to run the book and an investor portal under your own name are clients of the same Core, in the same deployment. See Tokenistry Backoffice For issuers

Licensed to you

For institutions. Your infrastructure, your keys, your data.

You have an environment, a risk function, and rules that apply to you rather than to a vendor's platform. Tokenistry Core runs single-tenant in your own cloud account. No shared control plane, no Tokenistry-operated service in the transaction path, no runtime dependency on us.

For institutions, and where the perimeter falls.

You retain control of

  • Cloud account, IAM and network
  • Database and application data
  • Custody workspace and policies
  • Private keys and signing authority
  • Contract administrative permissions
  • RPC credentials and chain access

Inside Tokenistry Core

Each owns one responsibility and one database. Adapters for custody and chains sit behind them.

01

Tokenization Engine

The instrument itself, with its controls enforced on chain.

 02

Transaction Engine

The durable path from a business decision to a confirmed transaction.

 03

Eligibility Engine

Who may hold, read by the token inside every transfer.

 04

Ownership Engine

Effective ownership and lineage, not wallet balances.

 05

Indexing Engine

Normalized chain state the other modules can rely on.
—

Supporting infrastructure

Custody and chain adapters, behind the modules.

Custody integration →

Technical detail

Architecture → What belongs in your product, what belongs underneath, and where the boundary is drawn. Technology → Rust on the wire, Solidity on settlement, and the properties each choice buys. Live demo → Issue, permission, distribute, reconcile and redeem against a real chain, one step at a time. Quickstart → Run the whole stack against a testnet, from one command.

What Tokenistry is not

Where local law makes register-keeping or safekeeping a licensed activity, that role belongs to your licensed provider and we supply the technology beneath it.

  • not legal or regulatory advice
  • not the issuer
  • not a broker or distributor
  • not a custodian
  • not a KYC or AML provider
  • not the register where that is licensed

Start here.

Issuing an instrument, planning a build of your own, or advising a client who is doing either: the conversation is with the people who wrote the software.

Submissions go to a Tokenistry address and nowhere else.

Two ways to run it.

We operate the infrastructure behind your issuance, or license it to run in your own environment. Same software either way.

Talk to us