Self-hosted crypto trading and market data tools

Where the process runs, and nothing else

This page answers one question: can you install it and run it yourself? Not what it costs, not what licence it carries, not whether anyone else can see what it does. Just where the process lives.

That is a narrower claim than it sounds, and it is worth separating from the one next door. Open source is about the licence on the code. This list is about the deployment. The two overlap heavily — nearly everything open source here is also runnable on your own machine — but they are not the same list, and the places they come apart are the most useful things on this page.

The twelve where the code is yours to run and not to read

These are the cards that make this a different list rather than a second door onto the same one. Each ships something you install on your own hardware under terms that are not open source.

Proprietary libraries you compile into your product. TradingView Advanced Charts is free to use and explicitly not open source — the repository is granted on application, the attribution has to stay visible, and the terms bar putting any part of it in a public repository. Highcharts Stock and ChartIQ are commercial licences, bought per developer seat and per year, that you then host yourself. DXcharts is the paid half of an open core — its free Lite edition is genuinely open, and the product with the indicators and the drawing tools is proprietary and quoted from 499 dollars a month. In all four cases the code sits inside your build and outside your control.

Source-available, which reads as open until you check. vectorbt is Apache-2.0 with a Commons Clause — you may read it, run it and modify it, and you may not sell it. That one added condition takes it out of the open-source definition and off the other page, while changing nothing about your ability to install it.

Its paid edition, vectorbt PRO, goes a step further: the licence is proprietary and the source is available to members, which means you install it from a private repository you keep access to by continuing to pay. Run it wherever you like; read it for as long as the subscription lasts.

A licence that can be withdrawn. dYdX v4 Clients carries a bespoke grant whose text reads like MIT but is conditioned on complying with the vendor's terms of use, with rights terminating automatically if you do not. The repository's own badge says AGPL and one package manifest says AGPL-3.0; only the Rust crate labels it honestly. Install it wherever you like — just do not call it open source on the strength of the badge.

Paid applications rather than libraries. Gunbot is the clearest case: a signed binary you install on your own machine. New buyers have paid for it by the month since October 2026, 29 euros for Gunbot Unlimited; the older lifetime licences, now sold only as upgrades to people who hold one, are registered on a blockchain against an ERC-20 wallet. You own the process, the server and the key file, and the source is not published. ProfitTrailer is the same shape: a closed Java application you run on your own Windows, macOS or Linux machine, or a Raspberry Pi. HaasOnline sells it as one edition of two — TradeServer is a licence you install on a machine you control, one active instance per licence, beside a cloud edition the vendor hosts. Gainium publishes its self-hosted edition's code, but under the Fair Core License, which bars a competing bot service, so it belongs with vectorbt above rather than on the open-source page. And tread.fi offers its execution engine in your own cloud with Docker, by request and at no published price. Everything else in this section is something you compile into your own product; these are the thing itself.

The one going the other way

L2BEAT is open source and is not on this list: the code is public and the product is a site somebody else runs. That is the shape most of the on-chain and market-data half of the catalogue takes, and it is why this page is dominated by engines rather than by data.

What self-hosting actually buys

Nobody else holds your keys. For anything that connects to an exchange account with trade permission, this is the whole argument. The key sits in a file on a machine you administer instead of in a vendor's database. That moves the risk rather than removing it — the security of that machine is now part of your trading system — but it is your risk to manage.

Nobody can change the terms under you. A hosted product's free tier can be retired, its price can move and its API can start requiring a key; six pages in what to use instead exist because exactly that happened. An installed binary keeps working on the terms you installed it under. What it cannot keep working without is its upstream data.

The feed is still somebody else's. This is the honest limit of the whole page. You can run the backtester, the bot and the chart yourself, and every price they draw still arrives over the network from a venue or an aggregator, on that vendor's terms and subject to that vendor's outage. Self-hosting buys independence from the application layer and none at all from the data layer.

What you take on

The machine, its uptime and its patches; the key file; and, for anything that trades, the fact that it has to keep running while you are asleep, which is a server rather than a laptop. The hosted versions of several products on this page exist precisely because that is real work, and paying somebody to do it is a legitimate answer.