What to use instead of TradingLite

The product

TradingLite was a browser order-flow terminal, and the heatmap was the reason people paid for it: a rendered picture of the limit orders resting in the book, price on one axis and time on the other, with the footprint, volume-profile and delta tools stacked around it. It had its own scripting language, LitScript, with a manual and a reference in the site's own navigation, and the home page as captured on 24 January 2026 advertised over 500 community-created tools, 15+ exchanges and 400+ pairs, three years of history, and a 14-day trial with no card. Its own description now puts the data at "more than a dozen exchanges".

It is over. The site today carries the word "Service ended" in its header, the line "Technology available for acquisition", and two sentences that settle the question: "The technology is for sale. The previous service will not resume." Lower down: "The platform is not currently operating." A section headed Former subscribers says the service operated by the previous company has stopped and will not be restored by it, that the page takes no payments and holds no account records, and that a card issuer or payment provider is the route for a payment method charged for a period without service. Read 19 September 2026. The footer dates the product 2018-2026.

The shutdown has no published date, so the one on this page is inferred and you should treat it as such. No announcement, changelog or status post gives one. What is dated is the evidence either side: the Internet Archive's last capture of the working product site is 24 January 2026, and on 12 March 2026 the origin answered the Archive with an nginx 504. The date in this page's header is that 12 March capture — the first dated proof the service had stopped answering. The real date is somewhere in the seven weeks between the two, and the operator dating its own product to 2026 is as close as its own words get.

This matters more here than it usually would, because the product still reads as alive everywhere else. Round-ups of the best crypto charting tools carrying 2026 in their titles still list it, and a reader can arrive at this page from a review published after the lights went out.

What to use instead

Start with the bad news, because every migration guide for this product omits it: nothing in this catalogue draws the heatmap for you. The tools below hand you the data it was drawn from, or the context that used to sit around it. Budget for a renderer, or for changing how you read the market.

If what you need is book data without writing an indexer, CoinGlass is the closest: L2 and L3 order-book endpoints across thirty futures venues, alongside the funding, open-interest and liquidation series. It is an API rather than a chart, it has no free tier, and the cheap plans coarsen the time axis — the $35 tier returns nothing finer than four-hour bars, which is not order flow.

If what you need is the book itself, exactly as it was, Tardis.dev is the one that has it: tick-level L2 and L3 snapshots and incremental updates from 64 exchange feeds back to 2019, as CSV or through a replay API. This is the honest reconstruction of a resting-liquidity heatmap, and it is a research tool — replay, not a live feed.

If you want it live and are prepared to write the client, CCXT streams normalised order books over websockets from 76 of its 104 exchange adapters under an MIT licence, which makes the multi-venue part of the problem free. The rendering, the price binning and the decay of old liquidity are yours.

If what you actually read on the screen was positioning rather than resting orders, Velo gives the cross-venue derivatives view — open interest, funding, basis, liquidations across Binance, Bybit, OKX, Deribit and Hyperliquid — in a hosted terminal you can open with a free account.

If you watched one pair on one venue, take the venue's own feed. The Binance market data API serves depth, trades and funding with no account and no key at all, and for a single symbol that is the shortest path from dead terminal to a chart of your own.

What you give up

The picture, and the two-week trial that let you decide whether you liked it. Resting liquidity is not a product anyone here sells; it is an output. A liquidation heatmap — CoinGlass publishes those — is a model of where leveraged positions would be closed out, which is a different claim about the market from "these limit orders exist right now at these prices". If you traded off the second and substitute the first, you have changed what you believe, not just your vendor.

The price band. TradingLite was a retail subscription with a free trial. The replacements split into things that are free and unfinished — CCXT, a venue API — and things priced for a desk: CoinGlass starts at $35 a month with coarse bars and the usable tiers are several hundred, and Tardis starts at $350 a month on the academic plan and $700 for a solo licence, before you have written a line of rendering code. There is no drop-in at the old price.

LitScript and the 500 community indicators. Every one of them was written against an interpreter that shipped inside a product that no longer runs, there is no export, and nothing in this catalogue reads that language. If your edge lived in a script somebody else published on the TradingLite forum, it is gone, and the only version of it you can still use is the one you understand well enough to write again.

Migration notes

A heatmap is a rendering problem, not a data problem, and the storage is the part people underestimate. You are replaying book deltas, binning resting size by price level and time bucket, and decaying it — one busy perp pair at full book depth is gigabytes a day from a tick archive. Decide the bucket size and the depth window before you buy the data, because both change the bill.

Check that your venue actually streams books before you plan around it. CCXT ships 104 REST adapters but 76 websocket ones, and support means an adapter exists rather than that the venue's book behaves; exchange.has is the thing to read, per venue, per method.

Venue APIs meter depth, and full depth is where the budget goes. On Binance's public endpoints an order book costs a weight of 5 at depth 100 and 250 at depth 5,000 — a fifty-fold difference behind one parameter — and the budget is counted against your IP, not your key, so a second process on the same machine shares it.

Redistribution was somebody else's problem and is now yours. A terminal held the licence to show you the venue's book; a screenshot from your own renderer, in a paid newsletter or a client-facing dashboard, is your redistribution. Binance's terms restrict it on both the flat-file archive and the live endpoints, and the other venues have their own. Read the clause before the chart becomes a product.