One platform. Six steps. Start where it hurts.

Every module runs on its own and delivers measurable value on its own. Adopt one. Add the next when it pays.

A person replies, not an autoresponder.

Six modules on one chain, one rail under all of them.

The steps follow the trust lifecycle in order: onboarding, identity, orchestration, consent, assurance, reuse. Each is a complete product with its own API surface and its own business case. What makes them a platform is what they share.

Themelion, the evidence rail

Worked example. Press play and six receipts are written, one per step.

How the six modules fit.

The shared fabric

Person, Account Holder, Data Subject, Visitor, Organisation, Subsidiary, Tenant Group. Every module reads and writes the same identity model, which is why they compound instead of merely coexisting.

Standalone by design
Each module solves one named problem at full depth and can be procured, deployed and retired on its own. No module requires another to deliver its day-one value.
Compounding by architecture
Modules discover each other when co-deployed: Metron grades what Pylon onboards, Kanon enforces what Synesis consents, Agora prices what Metron graded. Adding a module upgrades the ones you already run.
Provable by default
Themelion is not optional and not an add-on. Whichever single module you start with, you get the full evidence rail under it, which is what your auditors and regulators ask for first.

Module-shaped commercials, deployed on your terms.

How modules are priced

Platform fee per module: Per tenant and feature tier. Predictable, budgetable, and scoped to the modules you actually run.
Consumption: Per verification, screening, transmission and receipt, metered within each module, so cost tracks activity rather than headcount.
Trust reuse (Agora): The receiving entity pays to consume an assurance level the issuing entity paid to create. Inside a group this is a transfer-pricing line; in federation it is revenue.
Compliance packs: Jurisdiction-specific ruleset packs and white-label surfaces for Synesis and Kanon, licensed as add-ons.

Each module carries its own commercial schedule. Adding a module never re-opens the terms of one already deployed.

Deployment

On-premises, private cloud or hosted. Per module, on your infrastructure where policy demands it.
UK data residency available; residency and retention configured per jurisdiction.
No core-banking replacement, no migration. API or portal integration; modules and entities onboard one at a time.

In production

Proven in production at a systemic European bank: transmission to regulated subsidiaries with full consent management and audit trail.

Reference set shown: UK. EU and EEA equivalents on request.

Pick one module and we’ll put a number on it.

Four weeks, one module, two entities in your group, and one quantified result: onboarding time, drop-off, duplicated CDD cost, or consent coverage. It is the only honest basis for deciding what, if anything, to buy next.

Book a demo Find where to start