Vertalo is the software layer underneath your tokenization: one shared distributed ledger that serves as the securityholder register itself, connected to the broker-dealers, venues, custodians and chains you already work with. You decide who holds the transfer agent registration, which chains carry your assets, how your software connects, and whether anyone ever sees our name at all.
Chain-agnostic and jurisdiction-agnostic · Ethereum · Tezos · Aptos, and counting
An intermediary stands between you and an outcome and takes a position in it. Vertalo is software you licence, sitting underneath the outcome rather than inside it, and that is a structural fact about how the platform is built rather than a posture. Here is what it means concretely, and every row is checkable elsewhere on this site.
A page can only answer the general case. Describe yours in plain language, the way you would to counsel, and the advisor will tell you how it maps onto the platform: the engagement model that fits, the chain and jurisdiction picture, what you would need in place before starting, and what would drive the price. It is grounded in published regulation and the issuance runbooks rather than general web content.
Most platforms answer this question for you, either by being the transfer agent themselves or by never being one at all. Vertalo supports four arrangements, and what separates them is only which party holds the registration and whose assets are served on it. The protocol does not care which one you pick, so you can move between them as your business changes rather than choosing once at the outset.
Vertalo is the transfer agent of record and runs the full lifecycle from issuance through redemption, which is the shortest path when holding a registration yourself is not something you want to take on.
Vertalo operates behind the transfer-agent relationship you already have, adding digital and tokenization capability to your book while leaving that relationship and that book undisturbed.
You are the registered transfer agent and Vertalo is the software underneath you, with no transfer-agency relationship between us at all. The protocol has never depended on Vertalo holding that role.
You hold the registration and serve your own clients on the platform, keeping the client relationship and the regulatory standing, deployed inside your own cloud and security perimeter if that is where you want it.
We can put you into the tokenization business, or stay invisible underneath the business you already run.
The rules change at every border, governing who may hold a security, how transfers are restricted, and what has to be filed and when. The system of record underneath them does not have to change with them. Vertalo's ledger and the Vertalo Securities Protocol are chain-agnostic and jurisdiction-agnostic, so an American, British, European, Canadian, Singaporean or Hong Kong offering runs on the same record, the same controller model and the same API, while your counsel works from a different checklist in each one.
You can choose a chain, change it later, or run several at once, and the register stays where it is throughout. Chain, jurisdiction and platform remain three separate decisions instead of one irreversible bundle.
Where a deal calls for a local registrar or a transfer agent in its own jurisdiction, Vertalo runs underneath them and leaves them in place. A software platform is able to do that, because there is no competing mandate to negotiate around and no licence anyone needs to duplicate.
Which counterparties connect, and what authority each one holds, is a decision the platform enforces rather than merely records. The Vertalo Securities Protocol splits authority over a security into separate on-chain roles so that your counterparties can act on the ledger without any of them having to own it. Each of the flows you run maps to exactly one of those roles, covering primary distribution, secondary settlement, corporate actions and error correction, and you settle which role carries which flow during structuring rather than discovering it in production.
The issuer's authority over the security itself, covering what it is, how it is configured, and which rules govern it across its life.
Moves tokens between wallets and settles trades. The movements this role makes carry authority over the official book of record, because the role is held by a registered transfer agent, and which transfer agent that is follows from the engagement model you chose above.
Designates the balances a third party may move, which is what allows your ATS, your custodian and your broker-dealer to act on the register while the register itself stays in one pair of hands.
Your ATS can settle a trade, your custodian can reconcile a position and your broker-dealer can distribute an allocation, all of them working against the same ledger, and none of them needing to own it or to ask you for a spreadsheet first.
Every choice above rests on one thing that never varies. Vertalo's distributed ledger technology consists of the Vertalo Securities Protocol and the API architecture around it. SEC staff guidance issued on 15 May 2025 allows a registered transfer agent to use distributed ledger technology as its official Master Securityholder File without keeping a duplicate "digital twin" off-chain, and it contemplates a record that spans on-chain and off-chain components, which describes a distributed ledger with a queryable mirror alongside it. Because every party reads from the same book, there is never a second copy for anyone to disagree with.
A distributed ledger is infrastructure your counterparties can check for themselves, which is a materially different arrangement from asking them to trust that a vendor's database has stayed accurate.
Discrepancies between parties arise when each of them keeps a second copy, so a shared and immutable ledger removes the conditions that create them in the first place.
The ledger is mirrored into a queryable database so that your software gets sub-second reads, and that split between on-chain and off-chain components is the arrangement the guidance describes, with authority remaining on the ledger throughout.
The ledger is the register.
The controller model has a second layer to it. On chain, authority is split into roles, and at the API that same split runs as delegation, so your software or an authorized agent authenticates with credentials you were issued, discovers the role you delegated to it, and calls the tools belonging to that role and no others. From there it can issue and configure assets, record ownership, and tokenize and transfer, with each action written to the record as it happens.
"An AI touched the securities register" ought to be the most auditable event in your stack.
Built on the Model Context Protocol, the open standard for agentic software. Your backend connects with Vertalo-issued credentials using the MCP client library of your choice, and underneath it runs the same typed GraphQL API, 200+ operations, that has been in production since 2018.
Robinhood demonstrated that an agent can place a trade on a retail customer's behalf, and Vertalo carries that same idea into the part of the market where the official record itself has to change, so that an agent can issue a security, record who holds it, and move it between holders.
An agent can place trades on a customer's behalf, and the customer carries all of the resulting risk.
An agent can read data out of the platform but has no ability to write back to it, which covers the more straightforward half of the problem.
An agent can both read and write, working through role-scoped tools with human confirmation required on regulated approvals, against a single ledger of record.
Your price is set by how many assets you run and how many investors hold them, with both of those banded, so it stays where it is when your assets appreciate and when your investors trade. Each counterparty you connect carries its own price and none of them carries a meter, and MCP and API access is included in every tier, so the way you connect is never a separate line item.
For a company raising capital against a single asset, where one security, one cap table and one offering is the whole of the job, and where the transfer agency needs to be properly registered without a services firm assembled around it.
For managers running several vehicles at once who need a single ledger underneath all of them, along with live connections out to the places where their capital is raised and where their investors find liquidity.
For transfer agents and broker-dealers who intend to serve their own clients on Vertalo's platform while keeping the client relationship and the regulatory standing in their own name, at a scale where commitment materially changes the price.
Every tier runs on one of three deployments, and two of those have published floors.
Priced by how many assets you run and how many investors hold them.
An instance of your own, isolated from every other client.
Vertalo inside your perimeter, with a scoped implementation fee alongside the annual licence.
MCP and API access is included in every tier, because we would rather not work any other way, and because the integration is how the platform is delivered.
White-label arrangements exist because integration used to be too expensive to do properly, and that has stopped being true. What you build on Vertalo is your portal, your brand, your domain and your customer, running inside your own product rather than behind a redirect to ours. Taken all the way, your customers never meet Vertalo at all, and the platform is indifferent to whether you name it, which is the choice that proves every other one on this page.
The portal is yours and the register stays with us, and no Vertalo code ever crosses the wire between them, only data.
In August we handed a test client's plain-language brief to an AI agent that had nothing but Vertalo MCP credentials, and about three hours later it had built a branded issuer, investor and broker-dealer portal covering the cap table, documents, distributions, onboarding and the tokenization lifecycle, verified end to end. Deploying it into the client's own cloud account was its own day of work, and the recipe documents that day too. The client signed before the demo was public.
A click-through agreement gives you a tenant seeded with demo data and credentials on screen, free for six weeks, which is long enough to build something real.
Point your software at the sandbox endpoint using the credentials we issue, and it will discover your role and the tools that come with it on its own.
Start from our recipe and starter prompt, and expect a working portal in an afternoon rather than a quarter, with everything you build yours to keep.
Going live means a contract, real intake, holder migration and production credentials. Your sandbox work carries over, and your prior transfer agent's records either come with you or stay where they are with Vertalo underneath them.
Where securities regulation meets tokenization and transfer agency, research and analysis from the team at Vertalo.
The intersection of RWA, AI, and the SEC's January 2026 statement.
TechnicalWhy Move and the Aptos architecture advance institutional digital-asset infrastructure.
How-toA practical guide from traditional book-entry to digital.
Wavemaker Genesis Naples Technology Ventures Sputnik ATX Goren Holm Ventures Hampstead Park Capital CFC Capital Holdings Novablock Capital Sandbox access is open and free for six weeks, so bring your counterparties, your brand and whatever you want to build, and we will bring the register.
Tell us who you are and what you hold. A person reads every request.
✓ Request received
A person, not a queue, reads every request. We’ll come back to you within one business day.
30 minutes, no hard sell. We typically respond within one business day.
No spam. We reply within one business day.
We'll be in touch within one business day.