The terminal is open source.
Run it yourself in one command.
The same C++/WebAssembly terminal that powers the hosted product is public on GitHub: the same canvas, the same widgets, the same render loop, not a stripped community edition. A small MIT-licensed gateway feeds it Binance's free public market data, so the chart, DOM ladder, tape and liquidation Field run on your machine with no account and no API key. The layers computed from our recorded history stay hosted, and this page says exactly which ones.
$ git clone https://github.com/edgedepthhq/edgedepth-terminal.git
$ cd edgedepth-terminal
$ docker compose upThen open http://localhost:8080. Images are pulled prebuilt, so it starts in seconds; add --build to compile the WebAssembly from source.
1 second candles, built trade by trade in real time.
The gateway builds 1s / 5s / 15s / 30s candles from the raw trade stream. Each arriving trade updates the building candle and the live-price line, while the DOM and orderbook keep moving at full stream rate. The liquidation Field is computed client side from the same candles. All of it self-hosted, all of it free.
A free orderflow terminal, and a frontend for your own engine.
The open one in a paid category.
Serious orderflow tooling is closed, desktop-bound and subscription-priced, and the free end of the category is thin. This terminal is the open exception: a real chart engine, full-depth DOM ladder, tape, GPU orderbook heatmap and paper trading on a live feed, plus VPVR, TPO and footprint on any of the free replay packs, in a browser tab, from public data you don't pay for.
How it compares to Bookmap →A 180 FPS frontend for your own trading engine.
If you run a bot, you already have ingest, a book and fills. What you lack is a UI worth watching. The terminal accepts ?ws= and protos/messages.proto is the entire contract: emit trades, candles, book updates and stats from your engine and watch your own market render, your own fills on the tape. No charting library gets you this.
Read the wire contract →What runs self-hosted, and what doesn't.
If an empty panel sent you here, this is why it's blank. EdgeDepth is open core: the client is fully open, and every capability implemented by the community gateway and client works self-hosted. The remaining panels consume EdgeDepth analytics streams and the market history we record continuously across 660+ markets. Those services are not part of the community gateway, so the terminal leaves the panels empty instead of inventing substitute data.
- + Candlestick chart with real history · history from Binance REST klines
- + 1s / 5s / 15s / 30s candles · built trade by trade from the raw stream
- + DOM ladder and orderbook · REST snapshot plus diff stream, sequence checked
- + Trade tape
- + Mark price, funding, open interest
- + Liquidations and the liquidation Field · the Field is computed client side from candles
- + Paper trading and watchlist · all client side
- + Historical backfill, 1m and above · Binance REST klines
- + VPVR, TPO and footprint on the free replay packs · no account and no backend; a .edpack carries the per-price volume they need
- – VPIN and flow toxicity
- – Positioning and smart-money flow
- – Modelled liquidation heatmap and Levels
- – Pattern detection
- – Scanner composite scores
- – Contagion
- – Deep historical tick replay
- – VPVR, TPO and footprint on a live feed · measured 2026-08-15: they need recorded per-price volume, which a raw gateway stream does not carry, so these panels stay empty on live
- – Courses taught inside the terminal
Self-hosting shows you what is happening now. The hosted product keeps recording while your machine is off: Pro rewinds 30 days; Research rewinds and searches 90 days for matching occurrences and what followed. It is the same terminal, signed in: same layout, same canvas, nothing to migrate. Open the hosted terminal or see what each tier adds.
Add your exchange.
Everything Binance-specific in the gateway sits behind one Exchange interface; the hub only knows streams, candle aggregation and fan-out. Adding Bybit, OKX, Hyperliquid or any venue with public market data is one adapter package plus one registration line, and the CONTRIBUTING guide walks through it.
The exchange walkthrough →The research MCP server is open too.
The MCP server that gives Claude, Cursor and any MCP client deterministic search over the recorded history is MIT on GitHub. Reruns are free and every answer carries a reproducibility key.
Connect an AI agent →Self-hosting, plainly.
Is the self-hosted terminal a trial?
No. The terminal client is AGPL-3.0 and the gateway is MIT; together they run on Binance's free public market data with no account, no API key and no time limit. Everything listed under self-hosted is included. EdgeDepth's continuously operated record and proprietary analytics streams are the hosted product.
Why are VPIN, positioning, patterns, the scanner and contagion empty when I self-host?
Those panels consume EdgeDepth analytics streams that are not part of the community gateway. They depend on continuously operated history and analytics, so the self-hosted terminal leaves them empty instead of inventing substitute data. The wire protocol is public if you want to implement your own streams.
What does the AGPL license mean for me?
You can run, read, modify and self-host the terminal freely. If you distribute a modified client, or serve one to users over a network, the AGPL requires you to publish your changes under the same license. The gateway is MIT so it can be embedded anywhere, including in closed systems.
Can I point the terminal at my own trading engine?
Yes. The terminal accepts a ?ws= query parameter and speaks a documented protobuf-over-WebSocket wire format; the protos/messages.proto file in the repo is the entire contract. An engine that emits trades, candles, orderbook updates and stats lights up the chart, DOM ladder, tape and heatmap at 180 FPS.
Can I use an exchange other than Binance?
The gateway isolates everything venue-specific behind an Exchange interface, so adding Bybit, OKX, Hyperliquid or any venue with public market data is one adapter package plus one registration line. The CONTRIBUTING guide in the gateway repo has the walkthrough.
Do the 1 second candles work self-hosted?
Yes, live. The gateway builds 1s / 5s / 15s / 30s candles trade by trade from the raw stream, and the terminal updates the candle and live-price line as trades arrive. The community gateway currently backfills one minute and above through Binance REST; sub-minute history needs a recorded feed.
Clone it tonight.
One command gets you the terminal on live Binance data. The hosted product is there when you want the layers that need the record.