Engagement

Licensed software, integrated by the people who built it

Tokenistry Core is either operated by us or licensed and deployed into your own environment. Integration and support come with it either way. Specialist engineering is available where a programme needs it, and is not the product. Pricing is quoted per engagement.

How an engagement is shaped

01 · Entry

Architecture & Infrastructure Assessment

Target architecture, custody and transaction strategy, chain choices, which modules are actually required, and a build-versus-buy answer — including where the answer is to build it yourself.

Discovery

02 · Issuers

Operated by Tokenistry

We deploy and run Core behind your issuance. You hold the authority key, so nothing we operate can move an investor's position. No environment, no ops team and no deployment on your side.

Operated engagement

03 · Institutions

Tokenistry Core Deployment

License the modules you need and implement them in your environment: integration, configuration, testing and production rollout.

Software license + implementation

04

Managed Tokenistry Core

Updates, module maintenance, upgrades and escalation, while you continue to host production.

Recurring software / support

05 · Optional

Tokenistry Engineering

Dedicated engineers working to a design owned by the architects who built Core — extending it, or adding specialist capacity to a platform you already run.

Engineering capacity

Where the constraint is specialist throughput rather than software, that is blockchain engineering.

The application layer

Core assumes a product team on the other side of the API. Plenty of issuers do not have one and should not need one. Tokenistry supplies the layer above it as well — a backoffice to run the book, and an investor portal under your own name — as clients of the same Core, over the same versioned API, each owning its own schema.

Technical due diligence

Documents, not assurances. Produced against your deployment during evaluation and shared under NDA rather than published as a library.

  • service boundaries & interfaces
  • deployment topology
  • trust boundaries & threat model
  • key and role model
  • transaction state model
  • reconciliation model
  • upgrade governance
  • failure and recovery procedures

A walkthrough runs against a live deployment with your architects present.

Related

Tell us what you are issuing

We will tell you which of this you need and which of it you already have.

Discuss your architecture