Is the TradingView Charting Library free for brokers?

The basic library is free with attribution, but the Advanced Charts and Trading Platform tiers used by brokers are commercially licensed, and redistribution inside a white-label product raises separate licensing questions.

What are the alternatives to renting a charting library?

Either license a different vendor (ChartIQ, DXcharts) — which moves the ceiling but keeps it — or use a platform whose vendor owns the engine outright, so new chart features are one conversation instead of a feature request queue.

How long does it take to build a production chart engine?

Plan in years, not sprints. Flux took three generations to reach 1M candles at 120 fps with full indicator parity. That is exactly why building only makes sense when charts are the core of your product.

Build or rent: why we wrote our own chart engine

Most brokers rent their charts from TradingView or ChartIQ and call it a day. We spent years building Flux — our own engine that renders a million candles at 120 fps. Here is the honest math behind that decision.

Every broker's platform has a chart at the center of it. And in 2026 almost every broker rents that chart: a TradingView Charting Library license, ChartIQ, or one of the smaller embeddable libraries. The integration takes a week, the demo looks great, and the decision never gets revisited.

We went the other way. Bicut Terminal runs on Flux, our own chart engine, third generation — and it is the single most-questioned decision in our stack. "Why would you build charting in 2026?" Fair question. Here is the actual reasoning, with the trade-offs we accepted.

What renting really costs

The license fee is the smallest part. The real costs show up later:

Your roadmap is capped by someone else's roadmap. Want order markers that show liquidation previews? A depth heatmap fused with the candle series? A widget that replays a strategy's backtest on the live chart? With a rented library you file a feature request. With your own engine you ship it.
Performance is fixed at "good enough for everyone." General-purpose libraries are built for the median use case — a few thousand visible bars, one or two panes. Screener walls with a thousand live mini-charts, or scrolling through years of tick-dense history, are outside the design envelope.
The license travels badly. White-label redistribution, native app wrappers, and OEM deals all raise licensing questions. When charts are the core of what you resell, renting the core is a strange place to be.
Everyone's platform looks the same. Traders recognize a rented chart instantly. If your differentiation strategy is UX, you have outsourced your differentiation.

What building really costs

Honesty section. Building a chart engine is expensive in exactly the ways people warn you about:

It took us three generations to get it right. Flux 1 was a canvas prototype. Flux 2 hit performance walls at scale. Flux 3 — the one in production — renders one million in-memory candles at 120 fps with 10 chart types, 132 drawing tools and 49 indicators.
Indicator parity is a grind. Traders expect their RSI to match the RSI they see elsewhere, to the decimal.
You own every bug forever. There is no vendor to file a ticket with.

If charts are a feature on your platform, rent them. If charts are your platform — the surface your users stare at six hours a day — the math changes.

For most platforms, building is genuinely not worth it. We say that as the people who built one.

Where the math flips

Three signals told us building was right:

The chart is the product. In a trading terminal, every workflow starts and ends on the chart. News pins, signal markers, on-chart backtesting, voice-driven drawing — all of it needs deep engine access that embed APIs don't expose.
Scale demands broke the rented model. A monitoring wall of 1,000 synchronized live charts is a core feature of our Terminal. No embeddable library survives that.
We resell the stack. Bicut licenses the terminal to brokers under their brand. Owning the engine means one conversation about licensing — ours — instead of three.

The takeaway for brokers

If you are evaluating platforms, ask one question that cuts through every demo: "Who owns the chart engine, and what happens when I need something it doesn't do?"

If the answer involves a third-party roadmap, you now know the ceiling of your own roadmap. Our answer: the engine is ours, it ships inside your platform, and when you need a feature — we build it into the engine, not around it.