Open Architecture · Design principles
Bring your providers. Keep one book.
Depa runs the operations between the specialists you already use — identity, custody, liquidity, banks. Change any of them; the record stays where it is.
Principles
Operations
Liquidity, custody and rails are specialist jobs. Depa owns the operations between them, and says what it doesn’t do.
Bring your own
Keep the providers and contracts you already have. Don’t have one? Use ours. Same result either way.
Providers change. The record doesn’t.
Every provider sits behind a connector and one data model. Swap one and your accounts, entries and history stay put.
One identity, many providers
Checks from any KYC or KYB provider become one identity that The Watch applies on every rail.
Same rules on every connector
Every provider’s activity passes the same Watch rules and posts to the same book. No vendor gets an exception.
API-first, tenant by tenant
Everything the backoffice does is in the API, every event is a webhook, every statement exports. Each client runs in its own tenant, with its own rules, limits and approvals.
Identity Hub
Your KYC provider, or ours. One identity either way.
Connect the KYC and KYB provider you already contract, send checks through the API, or use Depa’s. Identity Hub turns the results into one identity per customer — the one The Watch uses on every account and every rail.
- Documents and expiry tracked in one place, whichever provider ran the check.
- Change provider without losing a customer’s history.
- KYB and the people behind the company on the same identity.
- Your provider
- Depa’s provider
- API upload
- Identity Hub
- One identity
- The Watch, every rail
Bring your own
Identity
Your KYC / KYB provider, through Identity Hub.
Custody
Your custodian or wallet infrastructure. Balances post to the same book.
Liquidity
Your liquidity partners or ours. Every fill is a journal line.
Banking
Your bank accounts or ours in 23 currencies. Recon runs against both.
How it connects
- Your provider
- Connector
- The Journal
- The Book
A connector is the only part that knows a provider’s API. Everything after it speaks one model.
In the machine
Everything either writes to the book — or protects it.
