Cryptocurrency Exchange Development for Licensed Firms and Firms Seeking a License
Protofire's crypto exchange development serves licensed and license-seeking firms. We build the client ledger, order records, custody and compliance integration around the engine you choose, and onchain venues your team runs. In 2021 Protofire built the DEX core and subgraph for Swarm Markets, a BaFin-licensed DEX at launch.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
A licensed exchange answers for the systems around its engine
A firm that runs a crypto exchange under its own authorization answers to its supervisor for more than the trading engine. The firm answers for client positions, order records, custody and the compliance decision on each transfer, whoever built the engine. Protofire's cryptocurrency exchange development builds those systems around the engine you choose. We also build onchain venues that your team runs, and we connect firms without their own license to a licensed provider's rail.
In the EU, the national transitional periods for crypto firms ended on 1 July 2026 at the latest (Article 143(3)). ESMA's interim register file, read on 16 November 2026, holds 404 entries without a withdrawal date. By our count of that file on that date, 22 of those entries list the operation of a trading platform, and 235 list custody.
Who owns each layer of a licensed crypto exchange
The firm decides, its vendors run the engine and custody, and Protofire builds the records.
Client channel and operating rules
Compliance decisions and key policy
Trading engine or provider
Custody, KYC and screening vendors
Client ledger and order records
Custody and compliance integration
Onchain venue contracts
MiCA asks a platform operator to link each order to its fills
A platform operator keeps its order data for at least five years or gives its supervisor access to the order book.MiCA includes the data "that link an order with the executed transactions that stem from that order" (Article 76(15)).
ESMA also takes in order data directly. On its MiCA page, ESMA says it operates the MiCA Digital Assets Surveillance System (MiDAS). MiDAS takes in order and transaction data from CASPs and generates alerts on potentially suspicious trading behavior. CASP onboarding to MiDAS is open.
For example, a custody platform can deliver the same deposit event twice. Fireblocks tells developers that a webhook endpoint "may sometimes receive the same event multiple times". An exchange that credits each event on arrival then credits the client twice.
A firm's records break in three places. A register that trails the chain shows a balance the firm cannot prove. After an engine replay, the order log has lost a link that MiCA asks for. A vendor changes, and neither the client notice nor the DORA register shows the change.
What a white-label crypto exchange leaves with the licensed firm
A white-label product supplies the trading engine, and the firm that runs the product keeps its duties under MiCA.AlphaPoint writes that a white-label provider "does the heavy lifting, offering everything from the trading engine to integrated liquidity solutions and tech support".
Under MiCA, a CASP that outsources "shall remain fully responsible for discharging all of their obligations" (Article 73(1)). The firm also needs direct access to the outsourced service's information, and an exit strategy (Article 73). A custodian CASP that uses another custody provider has to use a CASP authorized under Article 59 (Article 75(9)).
Before signing, a firm that buys a white-label engine asks the vendor two questions. How does the firm read the product's order and position data directly? How does that data leave the product at exit?
A platform operator may not deal on its own account on its own platform (Article 76(5)). A white-label product may include integrated liquidity. The firm's counsel reviews who supplies it.
ESMA reminds that MiCA prohibits CASPs from outsourcing or delegating certain services, notably custody, to entities that are not authorised as CASPs.
Three routes to a trading venue and who holds the license on each
A firm can offer trading on a provider's license, under its own authorization or on onchain contracts.
License holder
On a licensed provider's rail: A licensed provider holds the license.
Under the firm's own authorization: The firm holds a CASP authorization or has made an Article 60 notification.
On an onchain venue the firm runs: The firm's counsel decides whether the venue needs an authorization.
What executes trades
On a licensed provider's rail: The provider's rail executes the firm's client orders.
Under the firm's own authorization: A matching engine from a vendor or the firm's own team matches orders.
On an onchain venue the firm runs: Solidity contracts on an EVM chain run spot pools, perpetual markets or block-trade offers.
Who runs it after launch
On a licensed provider's rail: The provider runs the rail, and the firm runs its app and its books.
Under the firm's own authorization: The firm runs the venue under its own operating rules.
On an onchain venue the firm runs: The firm's team runs the venue.
What Protofire builds in cryptocurrency exchange development
Protofire builds the records and integrations around a firm's engine, and the contracts of an onchain venue.For a firm that already holds its authorization, our CASP page covers the client records in more detail.
Selling crypto on a licensed provider's rail
A firm without its own authorization can sell crypto on a licensed provider's rail and keep its own app and books. Protofire builds the crypto-as-a-service integration around the provider: order flow, core booking, a daily match and service records. We also build the move of a client book onto a firm's own authorization, with notices, snapshots and a three-way match before credit.
Client positions the firm can prove
The firm can prove each client's balance from its own register. Protofire builds the ledger with one position per client and asset, fed by fills, instructions and custody events. Firms with a ledger keep it.
Order records that hold up after an engine replay
The firm can answer a request for one order with its fills, after partial fills, cancels or an engine replay. Protofire builds the order and execution records in the data format that platform operators use, and connects them to the firm's engine.
Deposits and withdrawals booked once
Protofire books each event from a custody platform such as Fireblocks against its transaction ID, so a repeated event books nothing. A daily match compares client positions, vault balances and the chain at the same block height.
One recorded decision per transfer before custody signs
The firm's officers see one recorded decision per transfer, with its KYC, screening and Travel Rule answers. Protofire joins the vendors' answers into one outcome before custody signs or the ledger credits a deposit. We integrate vendors such as Chainalysis for screening, and Notabene or Sumsub for the Travel Rule.
An onchain venue on contracts your team runs
A licensed firm can run an onchain venue with its own team. Protofire builds the contracts, pool design, swap front end and subgraph of a spot exchange. The license holder can keep an allowlist of the wallets that may trade. We also build perpetual contracts with price adapters, liquidation logic, a front end and keeper code, and block-trade contracts between permitted wallets. Contracts Protofire writes go to an outside audit firm, and an audit is not a guarantee.
Our record: Swarm Markets, Uniswap v3 deployments and Glif Nodes
In 2021 Protofire built the DEX core (a Balancer fork) and subgraph for Swarm Markets and contributed to dOTC.Swarm Markets was a BaFin-licensed DEX at launch where only KYC-verified wallets trade. Swarm held the license. Swarm also ran KYC and permissioning. A licensed firm that adds an onchain venue with Protofire keeps the same split of roles.
Uniswap governance's official list of v3 deployments names Protofire as the deployer on Redstone, Zero, Cyber, Ink, Shape, Abstract, Flow and Stable. The list dates their recognition between May 2024 and April 2026. Our case page gives the current status of each one.
Protofire built Glif Nodes, a public Filecoin RPC service, and runs it. Filecoin's newsletter of 29 May 2024 thanked "the Protofire team for running Glif Nodes RPC". An exchange that adds a chain needs the same kind of service.
From the engine you chose to the first daily match
The build starts from the engine and vendors the firm chose.
- Step 1
What the firm brings
You bring your route, your engine or provider, your custody platform and your compliance vendors. Under NDA, you also bring a sample of order and position records with client identifiers removed. - Step 2
One client order followed on the discovery call
On the discovery call, Protofire follows one client order from receipt through matching and settlement to the client's position. Protofire's first written proposal names each record we build, each system we connect and each decision the firm keeps. - Step 3
Ledger and order records first
Protofire builds the client ledger and the order records first. The daily match and the compliance outcomes read from them. - Step 4
Custody platform and compliance vendors connected
Protofire connects the custody platform and the compliance vendors to the ledger. Each withdrawal instruction includes its order reference, and each transfer gets one recorded outcome before custody signs. - Step 5
The firm runs the system
The firm owns the code. The firm also keeps its operating rules, compliance decisions and key policy. Protofire's software prepares each custody instruction under the firm's credentials, and the firm's signers approve it. If the firm asks Protofire to operate nodes, monitoring or an integration after launch, we do it under a written scope.
How work with Protofire starts
Your operations and compliance leads can read the shared terms before the first call.
- Proposal
- In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
- Price
- Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
- Ownership
- Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
- After launch
- Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
- Access
- Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
- Licenses
- Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.
How we work shows a worked proposal.
Where an exchange build with Protofire does not fit
- You want a ready-made exchange. A crypto exchange script, a clone or a white-label product with its own engine comes from a white-label exchange vendor. Protofire builds what the firm's license asks for around the engine the firm has chosen.
- You need the license, the application or a legal opinion. Counsel and the competent authority decide the route. Protofire holds no financial or crypto-asset license, holds no client funds, keys or reserves, and gives no legal opinion.
- You want someone to run the venue, hold client assets, supply liquidity or make markets. Firms that the exchange appoints fill those roles. Protofire builds the systems that connect to them.
- You need a customer-liability proof of reserves or a trading front end for a centralized venue. Both builds are outside this service. The firm's bank or payment institution runs the fiat legs.
The build fits a firm that holds its authorization, is applying for it or sells on a provider's license. That firm has chosen its engine, custody platform or provider.
FAQ
What is crypto exchange development?
Who can build the systems around a crypto exchange for a licensed firm?
Should a firm build, buy or white-label a crypto exchange?
Does a white-label crypto exchange come with a license?
Can a licensed exchange add a decentralized or perpetual venue?
What does crypto exchange development cost?
Get a proposal
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.
