19 October 2026 · 4 min read

Open source crypto exchange software, and what it really costs

The code is free. The matching engine audit, the custody work, the chain watchers and the person who answers the pager are not. What you save and what you inherit.

Every few weeks somebody asks why they would pay for exchange development when there is open source exchange software on GitHub. It is a fair question with a specific answer, and the answer is not "because open source is bad".

What you actually get

Open source exchange projects generally give you a matching engine, a basic API, a reference front end and some chain integration. That is real value, and for a developer who wants to learn how an order book works it is the best possible starting point.

What they rarely give you:

• A maintained chain layer. Deposit detection, confirmation rules and reorg handling age faster than anything else in the system.
• An operator console worth using. Most projects ship an admin that was written for the maintainer, not for your support staff.
• A security history. Who reviewed the withdrawal path, and when.
• Anyone to ask. A project with its last commit two years ago is a snapshot, not software.

The costs that do not disappear

The licence fee going to zero does not change the other four lines on the invoice.

• Reading the code. Somebody has to understand a codebase they did not write well enough to be responsible for money moving through it. That is days, not hours, and it is the part people budget at zero.
• Custody. Address derivation per user, a hot and cold split, a sweep policy and multisig release. Most open projects hand you a hot wallet and wish you luck.
• Deployment. Database, cache, reverse proxy, TLS, backups that actually restore, monitoring that pages someone.
• The upgrade path. Either you track upstream, which means merging other people's decisions forever, or you fork and own it, which means you now maintain an exchange.

Free software is free to acquire and expensive to be responsible for. The price you avoid is the smallest number in the project.

When open source is the right call

Genuinely, it often is:

• You have a developer in house who will own it long term.
• You want to learn the domain before spending money.
• Your requirement is unusual enough that no commercial build fits, and you would rather start from working code than from nothing.
• You are building something non custodial, where the hardest part, holding other people's funds, is not your problem at all.

When it is the expensive choice

• Nobody on your team wants to own it, so it becomes the developer you hired for three weeks and then lost.
• You need to launch in a week. Reading an unfamiliar codebase is slower than building a familiar one.
• You want support when something breaks at 3am. There is nobody to call.

The honest comparison

A spot exchange built for you starts at $999 from scratch, or from $499 when it begins from a platform already built. Against that, "free" is only free if your own time is worth nothing and nothing goes wrong.

What you should insist on either way is the thing open source gives you by default and a bad vendor takes away: the source code, readable and unencrypted, in a repository you control. If a paid build does not give you that, open source is strictly better. If it does, you are comparing two pieces of readable code and the only question left is who maintains it. How to tell those vendors apart covers the rest.

Questions

Is there a good open source crypto exchange

There are several usable matching engines and reference implementations, and they are a genuinely good way to understand the domain. The gap is rarely the engine. It is the custody layer, the chain watchers and the operator console around it.

Can I launch a real exchange with free software

Yes, if somebody on your side owns it. The code is not the hard part. Being responsible for a withdrawal path you did not write is the hard part.

What does open source exchange software not include

Usually: production ready custody, maintained chain integrations with reorg handling, a console built for support staff, and anyone to call when it breaks.

Is it cheaper than paying a developer

Only if your time is free. A build from scratch starts at $999, which is less than the cost of a week spent reading somebody else's codebase.

Do I still own the code if I pay someone to build it

You should. Readable, unencrypted, in a repository you control, with no licence check phoning home. If a vendor will not do that, their offer is worse than the free alternative.

Can you build on top of an open source engine for me

Yes, and sometimes that is the right answer, particularly where a project already solves something unusual well. The work then becomes custody, console and deployment rather than matching.