DASHBOARD
Good morning, Org Admin.
What are we working on today?
Create a deal
or
Explore marketplace
All organisation deals · oversight SIMULATED
DEALS BY STATE
1
Draft
2
Open
3
Negotiate
1
Locked
0
Committed
4
Settled
CYCLE TIME · TARGET
Originate
2d
Assemble
9d
Design
4d
Execute
3d
VALUE TRANSACTED MOCK
$312M
Payment legs · from ledger events
Needs your attention
behind target closeCross-Border RepoAssemble · 18d9d past target→
Token Issuance · Series BDesign · 11d7d past target→
Inbound offers
Active deals
Tokenised Repo IVORY-6205
Blueprint: Intraday Repo · Ashvale debt instrument as collateral
Repo
Finance securities against cash — sold now, bought back later.
Required
Optional
V
P
C
R
Drag a seat down · click to fill · drag placed seats to reorder
Seats stay empty until you fill them
Fill seat
pick a participant
×
Deal roomSLATE-2000×
ActivityChatFiles
Org Admin created the deal room and set the Repo blueprint.
just now
Org Admin moved the deal into Open.
2m ago
Issuer - Main verified. Party id bound to the room.
4m ago
Files
×GMRA terms · draft
PDF · 2 days ago
Eligibility schedule
XLSX · 1 day ago
Ashvale term sheet
PDF · 6h ago
MARKETPLACE
Marketplace
DEFINITIONS
How Flowryd works
Flowryd is the orchestration layer for a multiparty deal room — the building blocks for transaction flows. Think of a kitchen redesign: you plan the layout and choose the units before anything is installed — what's needed, in what order, and what can wait. A deal works the same way. Here's the shared language for the pieces you build one from.
The building blocks
Blueprint
A reusable layout for a deal — the ordered steps, the role at each step, and the standards — with no firm names attached. You can take the layout without taking the parties.KitchenThe layout: where the sink goes, and the order it gets installed in.
Flow
A blueprint put to work: an ordered sequence of steps a deal moves through.KitchenThe job, from first fix to final sign-off.
Step
One point in a flow where something has to happen before the deal can move on.KitchenOne stage of the fit-out.
Seat
An open slot in a deal, labelled by the role it needs. It stays open until a party whose role matches takes it.KitchenA slot in the layout — fridge, oven, sink.
Role
What a seat requires a party to do — Custodian, Registry, Liquidity, and so on. One party can hold more than one role.KitchenThe trade: plumber, electrician, tiler.
Function
A capability a flow needs at a point in it — Oracle / Pricing, Compliance Check, FX.KitchenWhat has to happen there: plumbing, gas, ventilation.
App stack
A combination of parties that perform a set of functions — taken as one prefab component, instead of assembling and sequencing each yourself.KitchenA prefab unit — the sink arrives with the plumbing, waste and tap already in it.
Deal canvas
The working view where you arrange seats, stacks and steps before a deal goes live.KitchenThe floor plan on the table — where you move things around.
Deal room
The live deal: your chosen layout, your parties and your terms, moving through the lifecycle below.KitchenThe install — your layout, your suppliers, your terms.
How they nest
Function— a capability →App stack— parties that perform functions →Flow— steps where stacks fire.
Deal lifecycle · who acts
Draft
Flowryd
Assembling the deal — seats, terms and parties are still being set.
Open
Flowryd
Seats are published; any qualified party can take one.
Negotiate
Flowryd
Parties agree the terms and the fee split; Flowryd orchestrates the agreement.
Locked
By the parties
Each regulated party commits its own leg on its own rail, through its own application.
Committed
Flowryd
Every seat is filled and the terms are agreed. Flowryd commits the deal as green to go — orchestration streamlined, ready to execute. Flowryd's role ends here.
Settled
By the parties
The regulated parties settle the transaction themselves, through their own apps — for example on Canton. Flowryd never settles and never moves assets or cash.
Where Flowryd sits. Flowryd agrees parties and terms, and commits the deal once every seat is filled and the terms are agreed — the orchestration is streamlined and green to go. It never settles the transaction: settlement is executed only by the regulated parties, through their own applications and rails. Flowryd does not custody assets, does not move cash, does not transact on behalf of any party, does not decide liquidity and does not configure transfer agents. The orchestration fee fires at signature and is split among the participants — Flowryd holds none of it.
DEMO
Viewing as
Org adminMember with oversight
State
PopulatedEmptyLoadingError
Members
What each role can do
Party identifiers
A party identifier belongs to the organisation, not a person. Once it has been used in a deal it is permanent and case-sensitive — no rename, move or delete. Verification is set by the platform, never here.
Connected parties — network participants who I am connected to via multiparty deals
My Blueprints — workflow patterns I have created for closed deal rooms and or contributed to the public marketplace
Invite a member×
Signing authority
Off by default — signing is granted, never assumed.
What each role can do×
| Role | Organisation | Deals |
|---|---|---|
| Admin | Manage members and party identifiers | Deals they are in |
| Member | — | Deals they are in |
Two independent flags — set per person, on either role:
| Flag | Grants |
|---|---|
| Oversight | Sees all organisation deals — read and comment. Cannot advance state. |
| Signing | Can accept a seat and move a deal to Locked. |
Admin does not get oversight by default. Managing the organisation is not seeing the book — oversight is granted separately.
Signing binds the firm. It is granted per person, independent of role, and nobody can grant it to themselves.
Add a party identifier×
Case-sensitive. Stored exactly as typed — never normalised.
This is the last moment to catch a typo. Saved exactly as shown — it cannot be changed after saving.
Party identifiers are permanent and case-sensitive. Identifiers differing only by case are different parties.
Confirm×
Create a deal×
From scratch
Blank canvas — add roles and steps yourself.
From a blueprint
Start from a proven, ready-to-run flow.
Pick a blueprint