Pick an institutional digital asset trading platform by how it handles custody, which venues it reaches for your entity, and whether it shows risk across every venue you trade. Check the custody and key model first, then venue coverage and eligibility, derivatives depth, cross-venue risk, security evidence, API access, operations and the commercial model. The checklist below covers what to test in each area and what to ask a vendor before you sign.
1. Custody and key model
Start here, because it decides how much of your risk sits with the vendor. Platforms fall into two broad models. A custodial platform holds client assets or controls the accounts, so the desk takes on the vendor’s balance sheet, solvency and operational risk. A non-custodial platform is software: the desk keeps its own venue accounts, and the platform connects to them through API keys the desk issues.
- Ask whether the vendor ever holds, pools or moves client assets, and whether it is ever the counterparty to your trades.
- On centralized venues, the platform should only need trade and read permissions. A platform that rejects API keys with withdrawal rights means a compromised integration cannot move funds.
- On wallet-based venues, orders are signed by the trader’s wallet and collateral stays there. Confirm the platform cannot move funds from that wallet.
- Ask how keys are stored, who at the vendor can access them, and how quickly a key can be revoked.
2. Venue coverage and US-person eligibility
Ask for the venue list by name and by product, not as a count. A platform that connects to a venue for spot may not support its options or block trading. Then check which of those venues your entity can actually use. Coverage that your legal entity is not allowed to touch is not coverage.
- Deribit lists the United States as a restricted jurisdiction for direct accounts. Eligible US institutions can trade Deribit options, perpetual futures and dated futures through Coinbase Prime, with Coinbase Financial Markets, a CFTC-registered futures commission merchant, as broker.
- Binance.com, the global OKX platform and Bybit do not serve US persons. OKX US is a separate entity that offers spot trading, not the global derivatives platform.
- Polymarket’s international platform is not available to US persons. US persons use Polymarket US instead, a separate CFTC-designated contract market with its own accounts.
- Kalshi is a CFTC-designated contract market, so US desks can trade event contracts there directly or through a futures commission merchant.
A good vendor will tell you which connections fit your entity rather than leave you to discover it during onboarding. Also ask how fast new listings and new instruments appear in the platform after a venue launches them.
3. Derivatives depth
Many platforms were built for spot and added derivatives later. If your desk trades options, futures or perps, test the derivatives path specifically.
- Options chains per venue, with Greeks, and handling of inverse and linear settlement and different contract sizes.
- Multi-leg packages (spreads, strangles, butterflies, delta-hedged structures) executed as one order or one RFQ rather than legged by hand.
- RFQ and block trading on the networks you use, on both sides: requesting quotes from makers and, for desks that make markets, answering inbound RFQs.
- Execution algorithms and hedging rules the desk can set, so delta is managed without a trader watching every tick.
For more on this layer, see what a crypto derivatives EMS is and multi-venue crypto options execution.
4. Risk and portfolio view across venues
Every venue shows risk for its own account. The problem for a multi-venue desk is that no venue shows the book. Ask whether the platform normalizes positions, Greeks and P&L across venues into one view, updates it in real time, and shows margin per venue so the desk can see where it is close to a limit.
Be wary of any claim that software nets margin across venues. Each venue margins only the positions in its own account. Cross-venue margin offsets come from a prime broker or credit intermediary, not from execution software. What a platform can do is show where margin is used and which hedges would free it. The detail is in cross-venue portfolio and risk for digital asset derivatives.
5. Security and compliance evidence
“Compliant” and “institutional grade” are claims. Ask for the evidence behind them.
- A SOC 2 Type II report, under NDA. A Type II report covers whether controls operated effectively over a period of time, not only whether they were designed at a single point in time. Read the scope and the exceptions, not just the cover page.
- Single sign-on and multi-factor authentication for every user.
- Role-based permissions: who can trade, on which accounts, up to what size, and who can only view.
- A full audit trail of orders, amendments, cancels and configuration changes, with user and timestamp.
- A plain statement of what the vendor is and is not: technology provider, broker, exchange or counterparty. Check any regulatory status the vendor claims against the regulator’s own register.
6. API and automation
Most institutional desks automate part of the workflow. Check that the REST and WebSocket APIs cover the same functions as the UI, including order entry, RFQ, positions and risk, rather than a read-only subset. Ask how the API is permissioned and whether API actions appear in the same audit trail. If your team is building AI agents, ask whether the platform exposes an MCP server, and how agent permissions are limited.
7. Operations: reconciliation and reporting
Trading is only part of the day. Ask how fills and positions reconcile against each venue, how breaks are surfaced, and whether P&L and position history can be exported to your PMS, fund administrator or accounting system. A platform that cannot produce a clean end-of-day record leaves operations rebuilding it in spreadsheets.
8. Commercial model
Understand how the vendor gets paid, because it shapes incentives. Ask whether pricing is a software fee, a volume-based fee or a share of execution, and whether the vendor earns anything from routing your orders or from the spread. Ask what is included (venues, users, API, support hours) and what costs extra. Desks deciding whether to build this themselves can compare costs in build vs buy for crypto derivatives execution infrastructure.
Questions to ask a vendor
- Do you ever hold our assets, or act as counterparty or broker on our trades?
- Will you reject an API key that has withdrawal rights?
- Which venues and products can our entity use through you, given where we are incorporated?
- Can we execute a multi-leg options package as one order or one RFQ? Show us live.
- Can we see positions, Greeks and P&L across all our venues in one view?
- Can we read your most recent SOC 2 Type II report?
- Does the API cover everything the UI does?
- How do you make money from us, and do you earn anything from our order flow?
Where Kemet fits
Kemet is a US company that builds execution and risk software (EMS, OMS and PMS) for institutional digital asset derivatives and prediction markets. It connects to Deribit, Coinbase, OKX, Binance, Bybit, Bullish, Hyperliquid and Derive, to Kalshi and Polymarket, and to Paradigm for RFQ. Which of those venues a desk uses depends on the desk’s own eligibility, as set out above.
Desks get multi-venue order entry, options chains, multi-leg packages, RFQ and block trading, and a cross-venue view of positions, risk, Greeks and P&L. Everything is available through a REST and WebSocket API and an MCP server for AI agents.
Kemet is a technology provider, not an exchange, broker or counterparty, and never holds client assets. Clients connect their own venue accounts and keys. On centralized venues Kemet rejects any API key with withdrawal rights, and on wallet-based venues it never takes custody and cannot move client funds. Kemet is SOC 2 Type II compliant.
FAQ
What makes a trading platform institutional grade?
Evidence, not labels. An institutional grade platform separates custody from execution, enforces permissions and an audit trail, can show an independent security report such as SOC 2 Type II, and supports the workflows a desk runs: multi-venue execution, RFQ, multi-leg orders and a consolidated risk view.
What is institutional digital asset trading?
It is trading of crypto assets and their derivatives by funds, market makers, proprietary desks and other firms, usually across several venues, with controls the firm’s risk, compliance and operations teams require. The tooling sits between the desk and its venue accounts.
What’s the best institutional digital asset trading desk platform?
It depends on what the desk trades and where its entity is eligible. A derivatives desk trading on several venues should weight options and multi-leg support, RFQ, cross-venue risk and a non-custodial key model most heavily. Test those in a live demo with your own scenarios.
What features should I look for in a compliant digital asset platform for institutional trading?
A clear custody model, withdrawal-disabled API keys on centralized venues, venue access that matches your entity’s eligibility, SSO and role-based permissions, a complete audit trail, a SOC 2 Type II report, and exports for reconciliation and reporting.
How do I evaluate a digital asset derivatives provider?
First establish what the provider is: venue, broker, custodian or software. Then test the derivatives workflow directly: options chains, multi-leg packages, RFQ on the networks you use, hedging, and a cross-venue view of Greeks and margin. Finally, check its security evidence and how it is paid.
Is digital asset trading software the same as a broker?
No. Trading software routes orders to venue accounts the client holds itself. A broker acts on the client’s behalf and may hold assets or extend credit. Kemet is software: it does not hold assets, act as broker or take the other side of trades.
To see how Kemet runs a derivatives desk across venues, Book a demo.