Derivatives venue · engineering partner
Crypto derivatives exchange development,
engineered for real risk.
TrustChange is a crypto derivatives exchange development company for EU-facing crypto operators and licensed VASPs. We engineer the matching engine, the margin engine, the funding and mark-price pipeline, the liquidation engine, the trader and risk consoles and the compliance controls as bespoke software under your brand — not a SaaS licence with a per-seat fee. You get crypto derivatives exchange development services your risk team can defend and your auditor can read.
- EU-based engineers
- MiCA-aware architecture
- Deterministic liquidations
- AML & Travel Rule aware
- GDPR-aware storage
What "derivatives" covers here
Crypto perpetual exchange development services — and the products around it
Most searches for a crypto derivatives exchange development company are made by operators who need perpetuals first, then dated futures, then options as the risk framework matures. Below is the product matrix we build against — each product lands on the same matching, margin and risk spine, so nothing is bolted on later.
Building spot markets first? See centralized crypto exchange development and the pillar crypto exchange development. Company-level view: crypto software development company.
| Product | Description | Note |
|---|---|---|
| Perpetual futures | Linear or inverse, funding-rate based, isolated or cross margin | Most common starting point for new venues. |
| Dated futures | Fixed-expiry contracts with settlement schedule and mark-to-market | Adds a term structure and expiry logic to the engine. |
| Options | European-style calls and puts, with a pricing model and margin add-ons | Requires a mature risk framework — usually not phase one. |
| Leveraged tokens & spread products | Wrapped constructs settled against the same core engine | Downstream of a solid perp implementation. |
Product surface
Three surfaces in every crypto derivatives exchange development services engagement
A derivatives venue is not one app. It is the trader-facing derivatives product, the risk and liquidation console your team runs, and the APIs your market makers build against. We ship all three as one product, on one architecture, with one team accountable end to end.
-
01
Trader-facing derivatives app
Web and mobile derivatives UI under your brand: positions, margin, funding, unrealised P&L, order tickets, protective orders and liquidation warnings.
- Web + native mobile
- Advanced order tickets
- Position & funding views
-
02
Risk & liquidation console
The console your risk team runs the venue from — margin parameters, ADL settings, insurance fund exposure, liquidation queue, position limits and case work.
- Risk parameter editor
- Insurance-fund view
- Liquidation queue
-
03
APIs, market data & connectors
REST, WebSocket and FIX ingress for market makers, plus mark-price and index feeds and outbound market-data streams for third-party integrations.
- FIX 4.4 · REST · WebSocket
- Mark-price / index feeds
- Rate-limit & replay logs
Stack
What sits behind a crypto derivatives exchange
Eight layers, one system. Every layer names an owner, a control and a piece of audit evidence — nothing is left implied under the "derivatives" label.
Related specialised builds: crypto matching engine development, crypto liquidity infrastructure development, crypto exchange infrastructure development, white label trading platform development.
| Layer | What we build |
|---|---|
| Matching engine | Deterministic, replayable order book with pre-trade risk on notional and margin availability Fills reference resting orders; a trading day can be reproduced from the event log. |
| Margin engine | Isolated and cross margin per account, with initial and maintenance margin per product Margin is recomputed after every fill, funding tick and price update. |
| Funding & mark price | Funding-rate calculation, mark-price computation and index composition across vendor feeds Every parameter version and vendor input is stored with the tick that used it. |
| Liquidation engine | Deterministic liquidation queue with partial fills, ADL fallback and insurance-fund contribution Liquidations follow a written policy; every step writes to the audit log. |
| Custody & settlement | MPC or HSM signing for on-chain movements, cash-settled positions on the venue ledger Customer collateral sits under your custody, not on-chain in the user's control. |
| Compliance controls | KYC/KYB with product suitability gates, sanctions screening, Travel Rule on transfers Suitability gates apply per product; every decision writes to the audit log. |
| Market surveillance | Rule-based alerts for wash trading, layering, spoofing and index manipulation with case files Analyst queues and export bundles formatted for supervisor requests. |
| Runtime & delivery | EU-hosted, CI/CD pipelines, observability, 24/7 on-call cover Your identity provider, your key custody, your data regions. |
Margin & liquidation path
From order to settled P&L
Every position on the venue moves through the same margin, funding and liquidation gates. The parameters are yours to tune; the pipeline never skips a step. Speed comes from tuning, not from trusting the caller or the last vendor tick.
- 01
Order & risk
Sub-millisecond
The order arrives; pre-trade checks confirm the account has margin for the intended position change.
- 02
Match
Deterministic
The matching engine writes the fill to the event log; positions and margin recompute immediately.
- 03
Funding tick
Scheduled
Funding accrues per position on the configured schedule; each tick carries the rate version that fired.
- 04
Mark & unrealised
Continuous
Mark price and unrealised P&L update from the index feed; margin ratio is recomputed on every tick.
- 05
Liquidation gate
Sub-second
Positions below maintenance margin enter the liquidation queue; the engine partial-fills or defers to ADL per policy.
- 06
Settle & report
Session-bound
Cash-settled changes post to the ledger; export bundles publish for finance, risk and the auditor.
Delivery
How we deliver a crypto derivatives exchange development project
Five steps, in this order. Derivatives work runs inside the product backlog — no separate risk phase bolted on before launch, no big-bang release of an untested perpetual engine.
- 01
Scoping
Weeks 1–2
We map products (perps first, then dated, then options), margin model, funding formula, index composition and the risk you must stand behind. Output: a scope, a control map and a costed plan.
- 02
Architecture
Weeks 3–4
Matching topology, margin engine, funding and mark pipelines, liquidation policy and surveillance rules written down first. Regulatory constraints shape the design.
- 03
Build
Two-week sprints
Matching, margin, funding, mark, liquidation and admin ship in slices. Property-based tests exercise the engine against adversarial market conditions.
- 04
Hardening
Before launch
Replay against historical stress days, load work, matching-engine and liquidation drills, and a third-party pen-test window. Insurance-fund and ADL scenarios are rehearsed with your risk team.
- 05
Launch and run
Cutover + ongoing
Named engineers on 24/7 cover during the first months. Runbooks, dashboards, market-halt playbooks and the audit log are handed to your team on day one.
Engagement
Four ways to buy your crypto derivatives exchange build
Same engineers, same standard. Only the commercial shape changes.
-
Fixed-scope build
A defined derivatives venue at a fixed price and date. Best when products and risk model are settled.
-
Dedicated team
A standing squad with a lead. Best for long roadmaps and new products each quarter.
-
Staff augmentation
Senior engineers inside your team. Best when you already own the plan and need matching-engine and risk depth.
-
CTO advisory
Architecture and buy-vs-build review before you commit. Best at the design stage.
Questions
FAQ: crypto derivatives exchange development
Six answers up front on scope, products, off-the-shelf vs bespoke, margin & liquidation, MiCA/AML/suitability and ongoing support. Bring the rest to the call.
What does crypto derivatives exchange development cover at TrustChange?
We engineer a bespoke, client-owned crypto derivatives venue end to end: the matching engine, the margin engine, the funding and mark-price pipeline, the liquidation engine, the trader and risk consoles, the compliance controls and the audit trail. It ships as source code in your repositories, with the IP assigned to you. TrustChange is a crypto derivatives exchange development company, not a SaaS vendor and not a legal-advice provider.
Which derivatives products do your crypto derivatives exchange development services support?
The reference build covers perpetual futures (linear or inverse, funding-rate based) with isolated and cross margin — this is where most new venues start. Dated futures add expiry logic and mark-to-market. Options are engineered on the same core once the risk framework is mature. Leveraged tokens and spread products settle against the same engine. Each product is a scoped module against the same risk, ledger and screening spine.
How is your crypto perpetual exchange development services different from an off-the-shelf provider?
Off-the-shelf perp platforms bundle a fixed engine and a licence fee, and the risk parameters live on the vendor's side. TrustChange as a crypto perpetual exchange development company engineers the matching, margin, funding and liquidation logic against your product design, your risk appetite and your audit expectations. A bespoke build takes longer up front, but you keep every rule, every parameter and every ADL decision.
How do margin, funding, mark price and liquidations work on the venue you deliver?
Margin is recomputed after every fill, funding tick and price update, per product and per account (isolated or cross). Funding rates follow a configurable formula against an index built from vendor feeds you choose. Mark price is a separate, tunable input designed to be robust against thin books. Liquidations run a deterministic queue with partial fills; auto-deleveraging (ADL) is the documented fallback when the insurance fund cannot absorb losses. Every parameter version is stored with the tick that used it.
How are MiCA, AML/Travel Rule and product-suitability rules engineered into the derivatives venue?
TrustChange is an engineering partner, not a law firm — your legal advisers set the policy, we ship the controls and the evidence. That means KYC/KYB flows with product-suitability gates, sanctions and wallet-risk screening before signing, Travel Rule data on crypto transfers, market-abuse controls tuned for derivatives (spoofing, index manipulation), and GDPR-aware storage with retention rules. Nothing about licences, authorisations or supervisor approvals is claimed on your behalf.
Do you also run the derivatives venue after launch, or hand it over?
Both are on the table. Most clients start with named TrustChange engineers on 24/7 cover during the first months while their own team ramps up — derivatives infrastructure is not a place to run thin on cover. They then take the platform in-house with runbooks, dashboards, liquidation playbooks and the audit log. Some keep us on as a dedicated development team or on staff augmentation for new-product, risk and control roadmap work.
Book a discovery call for crypto derivatives exchange development
Bring the product list, the margin model, the index composition, the licence context and the launch date. We come back with a control map, an architecture view and a costed plan for a venue you own end to end. No demo theatre.