შინაარსზე გადასვლა
guide8 ნოემბერი, 2026 · 9 min read

Open-source crypto exchange software in 2026: what you actually get and what it costs to productionise

OpenDAX, Peatio, OpenCEX and exchange-core checked on 8 November 2026: licences, last commits, runtimes past end of life, and the work to run one.

BitPolaris Engineering

English original

Open-source crypto exchange software gives you a matching engine, an accounts ledger, a basic web front end and the right to change all of it, at no licence fee. What it does not give you, in 2026, is maintenance: the best-known projects are either marked as unmaintained or have not changed in years, and they run on language versions that stopped receiving security fixes in 2022 to 2024. That does not rule them out. It means the real price of an open-source exchange is the engineering needed to modernise, complete and secure it, and the team to run it afterwards. This guide shows what we found in the main projects on 8 November 2026 and what it takes to put one in front of customers.

Method: we cloned each project’s public GitHub repository on 8 November 2026 and read its licence file, README, runtime versions and the date of the last commit on the default branch. Other branches and forks may be more recent. End-of-life dates come from endoflife.date. We did not install or test the projects, so feature lists are the authors’ own. BitPolaris prices are in EUR from our pricing page; cost estimates are labelled as ours.

What open source means for an exchange

“Open source” is used loosely in this market. Three different things are sold or given away under the label:

  • Open-source licence. Code published under a licence such as Apache-2.0 or MIT that lets anyone use, modify and run it commercially, without warranty. This is what this article covers.
  • Source-available or source-code licence. A commercial vendor gives you the code under a paid licence that limits redistribution. You can read and change it, but it is not open source. BitPolaris sells this, as do several vendors in our vendor comparison.
  • “Clone scripts”. Low-cost packages sold on marketplaces, often with obfuscated or partial code and a single-product licence. Our script versus software guide covers them.

A fourth group, peer-to-peer and decentralised exchanges such as Bisq (AGPL-3.0, last commit 5 November 2026), is open source and active, but it is a different product: there is no operator holding customer funds, so it is not a base for a licensed custodial venue.

The projects, checked on 8 November 2026

Project What it is Licence Last commit on default branch Runtime Status
OpenDAX (Openware) Container distribution that assembles Peatio, Barong (identity) and a front end Apache-2.0 23 February 2023 Ruby 2.6.6 Public repository inactive; Openware now markets OpenDAX Aurora as a separate product, priced on request
Peatio (Openware fork) Rails accounting core and market configuration; “a fork of Peatio designed for micro-services architecture” MIT 22 February 2023 Ruby 2.6.6, Rails 5.2.4 Inactive
Barong (Openware) Authentication and KYC service used by OpenDAX Not checked in detail 15 June 2021 Ruby Inactive on default branch
OpenCEX (Polygant) Packaged exchange: custodial wallet, matching engine, pro and swap interfaces, admin Apache-2.0 19 March 2026 (README edit; last code release 1.5.1 on 2 November 2023) Python 3.8, Django 3.2.7, Vue and Nuxt README: “This repository is not maintained. The code is provided as-is.”
exchange-core Java matching engine and risk module built on LMAX Disruptor; a library, not an exchange Apache-2.0 14 May 2022 Java Inactive

HollaEx also described its kit as open source in the past; the repository linked from its pricing page was not publicly reachable when we checked, so we leave it out.

The pattern is clear. OpenCEX is the most complete package and the most recent, and its authors now say it is not maintained. The Openware repositories have not moved on their default branches since early 2023, while the company markets a newer product. exchange-core is a matching-engine library that publishes latency figures in its README, but it has no wallets, no user accounts and no interface.

What a kit gives you on day one

Read the OpenCEX README as an example of a complete kit. It lists a custodial wallet for BTC, ETH, BNB, TRX and USDT on three chains, an order matching engine with four trading pairs, a professional trading interface, a simplified swap view, KYT screening if you bring Scorechain keys, KYC if you bring Sumsub keys and SMS two-factor if you bring Twilio keys. Installation is a shell script on a root server with at least 4 cores and 16 GB of RAM, and you supply your own cold-wallet addresses, chain-data API keys, SMTP service and reCAPTCHA.

That is a working demonstration of an exchange. For a hobby venue or an engineering prototype, it is a reasonable start. For a business that needs a licence, a bank account and customers’ money, it is the start of the work, not most of it.

What is missing before customers can use it

Compare the kit with what a regulator, a bank and an auditor will ask to see. The RFP checklist has the long version; these are the gaps that take the most time:

Area Typical open-source kit What a licensed venue needs
Runtimes and dependencies Ruby 2.6 and Rails 5.2 (end of life 2022) or Python 3.8 and Django 3.2 (end of life 2024) Supported versions with security fixes, and a dependency update process
Custody Hot wallet plus cold addresses you supply Hot, warm and cold tiers, key ceremony, M-of-N approvals, whitelists with delays, reconciliation against the chain
Operations console Basic admin KYC queues, withdrawal approvals, roles, maker-checker, a tamper-evident audit log, reports
Chains Public APIs (Infura, TronGrid, Etherscan) RPC pools with failover, node monitoring, reorg handling
Liquidity Empty order books; OpenCEX added a Hummingbot wizard in 2023 Market makers or a hedging engine, with risk limits
Apps Web only iOS and Android apps that pass store review
Monitoring and recovery Not described Alerting, on-call, backups to a second site, tested restores, recovery targets
Security evidence None published An independent penetration test and remediation record before launch
Compliance data KYC and KYT hooks Travel Rule data capture, sanctions screening, regulatory reports

Each row is a project. The runtime row comes first because nothing else is safe to build on an end-of-life stack: upgrading a Rails 5.2 application to a supported Rails version, or Django 3.2 to a supported release, touches every module and has to be done before any penetration test is worth paying for.

What it costs to productionise

The licence fee is zero; the work is not. In our cost comparison we estimate €300,000 or more of engineering and six to twelve months with a team of four to six before a kit can serve customers. That is our planning estimate from building and running an exchange stack, not a market statistic, and it assumes an experienced team. The main items:

  • Modernisation: runtime and framework upgrades, dependency replacement, and a security review of what you inherited.
  • Custody and the operations console: usually the largest single block, because it is what regulators and auditors examine.
  • Chain integrations: each chain needs its own node or RPC strategy, fee handling and failure cases; our RPC failover write-up shows what that involves for one stack.
  • Apps, monitoring, backups and the penetration test.

After launch, the cost does not stop: someone has to follow security advisories for every dependency, because there is no upstream maintainer doing it for you.

A commercial licence is the opposite trade. You pay a fixed price for software that already runs an exchange, and you inherit its design. For comparison, BitPolaris lists the exchange block at €24,500 one-time self-hosted plus €4,900 a year for updates and support, or €58,100 for a perpetual source-code licence with the right to fork and an optional update stream at 15% a year. The self-hosted buyer’s guide explains what each includes.

When open source is the right choice

Open source can still be the right route. It fits when:

  • your team is engineering-led, has run financial systems before and wants to own every line;
  • you are building a venue for an asset class or market structure no vendor supports;
  • you are prototyping to learn, with no customer money at stake;
  • you need a matching-engine library inside a larger system, which is where exchange-core fits.

It is the wrong route when the timeline is set by a licence application or a funding round, when there is no one on the team to own security patches, or when the plan assumes the kit is “nearly ready”. If you go this way, fork into your own organisation, pin and upgrade the runtimes first, and budget for an independent code review before you build on it.

Questions to ask before you build on a kit

  • When did the default branch last change, and is the project still maintained by anyone?
  • Which language and framework versions does it pin, and are they still supported?
  • Who will receive and act on security advisories for the dependencies?
  • How does it store private keys, and can it run a key ceremony and M-of-N approvals?
  • What does the admin console log, and could an auditor rely on it?
  • What does the licence say about warranty, trademarks and attribution?

Open-source crypto exchange software FAQ

Is there free open-source crypto exchange software?

Yes. OpenDAX and OpenCEX are published under Apache-2.0 and Peatio under MIT, so the code is free to use commercially. On 8 November 2026, however, OpenCEX’s README said it was not maintained and the OpenDAX and Peatio default branches had not changed since February 2023, so the cost moves from the licence to the engineering.

Is OpenDAX still open source?

The public OpenDAX repository is still under Apache-2.0, but its default branch last changed on 23 February 2023. Openware now markets OpenDAX Aurora as a commercial product sold through a contact form, so the public code and the product the company sells are no longer the same thing.

Can a licensed exchange run on open-source software?

A regulator licenses the business, not the code, so open source is not ruled out. The regulator will still ask for custody controls, an audit trail, monitoring, recovery and a penetration test, and you have to build or add those to a kit before the application. What regulators ask for lists the usual technical file.

How long does it take to launch an exchange on an open-source kit?

We estimate six to twelve months with an experienced team of four to six, most of it spent on modernising the stack, custody, the operations console, chain integrations and security testing. The licence process, banking and app-store review run in parallel and can be longer.

What is the difference between open source and a source-code licence?

An open-source licence lets anyone use, change and redistribute the code, without warranty or support. A source-code licence is a commercial contract: you get the code, the right to modify it for your own use and usually updates and support, but you cannot republish it. BitPolaris sells the second kind at €58,100 for the exchange block.

BitPolaris licenses the production software behind a live exchange, with the operations console, custody, chain integrations and apps in place, for your own servers or as source code. Prices are public.

See the Exchange block · Pricing

Sources

  1. Openware, opendax (LICENSE, README, .ruby-version), peatio (LICENSE.md, README, .ruby-version, Gemfile.lock) and barong, default branches cloned 8 November 2026
  2. Openware, openware.com (OpenDAX Aurora, OpenFinex), read 8 November 2026
  3. Polygant, OpenCEX (LICENSE.md, README, commit history), cloned 8 November 2026
  4. exchange-core (LICENSE, README), cloned 8 November 2026
  5. Bisq, bisq (LICENSE), cloned 8 November 2026
  6. endoflife.date, Ruby, Rails, Python and Django, read 8 November 2026
  7. BitPolaris, pricing, list prices as of 8 November 2026, and What crypto exchange software costs (cost model and assumptions)

OpenDAX, Peatio, Barong, OpenCEX, HollaEx and Bisq are names of their owners; this article describes their public repositories and implies no affiliation.

guide · 6 წუთის საკითხავიSelf-hosted კრიპტობირჟის პროგრამული უზრუნველყოფა: რას იღებთ, რას მართავთ და რა ღირსრას მოიცავს self-hosted კრიპტობირჟის პროგრამა, რა უნდა მართოს თქვენმა გუნდმა, რით განსხვავდება white-label ღრუბლისა და ღია კოდის ნაკრებისგან და რა ღირს.cost comparison · 9 წუთის საკითხავიკრიპტობირჟის პროგრამის მომწოდებლების შედარება (2026): განთავსება, საჯარო ფასები, ლიკვიდობა და გასაღებებიკრიპტობირჟის პროგრამის 14 მომწოდებელი გვერდიგვერდ, მათივე გვერდებიდან 2026 წლის 1 ნოემბერს: განთავსება, საჯარო ფასები, ლიკვიდობა, გასაღებები, აპები, ვადები.cost comparison · 9 წუთის საკითხავირა ღირს კრიპტობირჟის პროგრამული უზრუნველყოფა 2026 წელს: open source, white-label, საკუთარი შემუშავება, ლიცენზიაბირჟის მიღების ოთხი გზის საჯარო ფასების დიაპაზონები და ფარული ხარჯები: ლიკვიდობის კაპიტალი, ოპერაციები, კასტოდი, აპების მაღაზიები.

დაჯავშნეთ 30-წუთიანი შეფასების ზარი

Crypto exchange, payments, wallet, custody and token launch software, already running in production. Run it on your own servers, license the source code, or let us host it under your brand.