Price and indicator conditions
Cross, cross-up, cross-down, above, below, and a condition against another plot. Set from the chart or from the plot you are looking at.
The numbers below are read at build time from the registries that decide them — the chart types the renderer knows, the tools in the palette, the studies in the indicator library. If one of them changes, this page changes with it, because there is no copy of it here to fall out of date.
Ten renderings of the same series, thirteen intervals on the menu, and any interval that folds cleanly from what is stored. Nothing here is a separate product mode — every chart type takes every indicator and every drawing tool.
All ten are time-indexed, which is what lets a drawing, an alert and a replay cursor all refer to the same bar. Renko and its price-indexed relatives are deliberately not in v1: they emit a variable number of bars per unit of time, which breaks the assumption three other subsystems are built on.
One-minute, one-hour and daily bars are what exists on disk. Every other interval is aggregated from them in the database at read time, so an interval nobody else offers costs a query rather than a new feed — and how far back you can scroll is a number we set rather than a vendor’s.
Validated against external ground truth rather than against ourselves — and every one of them states, in writing, which convention it implements and which it rejected.
“Why does your RSI differ from theirs in the first fortnight” is the support question an indicator library exists to be able to answer. So the convention is a required field on every study — the registry refuses a definition with an empty one — and it is shown in the settings dialog beside the parameters, not buried in documentation.
The strongest evidence we have is external: this guide prints Wilder’s own 1978 RSI column beside the output of the engine that runs on this site, computed when the page is built.
Thirty-one tools in the palette, in the order they appear in it. Every one of them stores prices and timestamps — never pixels and never bar indexes.
This is the one structural claim in the product worth reading twice, because almost every alerting bug in this domain is a version of the same thing: the chart and the evaluator being two implementations of one indicator.
Cross, cross-up, cross-down, above, below, and a condition against another plot. Set from the chart or from the plot you are looking at.
A trigger is unique on the alert and the bar it fired for, so running the evaluator twice over the same bars produces one record and one notification, not two.
In-app, by email, or POSTed to a URL of yours and signed with your secret — with a record of every fire and every delivery attempt.
Layouts, replay, export and the read API. What each plan includes is on the pricing page, read from the same table the server enforces.
Up to 4 charts in one arrangement, with symbol, interval, crosshair and time-range linking — so moving the crosshair on one moves it on all of them. Saved layouts are named and returned to; the working chart never counts against the allowance.
A data-source swap behind the same interface the live feed uses, rather than a slice of an array — which is why no indicator can peek ahead. A repainting study at the replay cursor reads exactly what it would have read at the time.
The candles behind any chart, exactly as they were drawn, at the interval you were looking at. We ingested them into our own store, so there is nobody to ask.
Candles and instruments over /api/v1, authenticated with a key you mint and can revoke, with a per-key request budget so one runaway integration cannot spend the whole workspace's allowance. On Premium.
Served from our own rollup table rather than from a metadata API, which is why the search box answers on every keystroke instead of being rate-limited by somebody else’s free tier.
A read-only snapshot at an unguessable URL, and an embeddable version for a page of yours. Both carry the charting library’s attribution, because a chart inside somebody else’s iframe is exactly the case that requirement exists for.
The top tier holds 25 saved layouts, 25 indicators on a chart, 500 active alerts and 40,000 bars of history. Every limit is on the pricing page.
Four things stated plainly, because finding out on day three is worse than reading it now.
No order ever leaves this building and there is no broker integration on the roadmap. That also means none of the registration, suitability or best-execution obligations that come with routing one.
Public crypto venues, ingested into our own store. No licensed equity, futures or FX feeds — bring your own provider key for a daily equity series, on a free tier that allows 25 requests a day.
Nothing we ship is named after or compatible with Pine Script, and there is no transpiler. Indicators are a typed registry with their own parameter format; custom indicators, when they arrive, will speak that.
There are no signals, no scores and no suggestions about what to buy or sell anywhere in this product. It draws what happened and tells you when a condition you defined became true.
A public chart needs no account and serves real history from our own store, with every chart type and every indicator on it.