Developers
Build with the charting and market-data stack behind mmflow
Embed crypto charts, connect to mmflow's read-only market-data APIs, bring your own data feed, and reuse the same order-flow primitives that power the terminal. A typed, embed-first SDK: hardware-accelerated WebGL2 rendering, React & Vue bindings, custom indicators via defineIndicator, white-label theming, and real-time clients for JS, Python, Go, and Rust.
Playground
The real @mmflow/charts engine fed live mmflow data — the exact packages you embed, running in the browser.
Benchmark
Stream synthetic OHLCV into the WebGL engine and watch the frame rate hold as the point count climbs.
Data API
Production REST + SSE endpoints, the WebSocket gateway protocol, OpenAPI, and JS / Python / Go / Rust SDKs.
Packages
Install what you need — the core engine is framework-agnostic.
@mmflow/chartsFramework-agnostic WebGL2 engine + createChart, defineIndicator, createDataFeed, theming.@mmflow/reactTyped <Chart/> component + hooks.@mmflow/vueTyped <MmChart/> component.@mmflow/indicatorsExact, tree-shakeable indicator math — SMA, EMA, VWAP, RSI, MACD. Zero dependencies.@mmflow/sdkcreateMmflowFeed() for live REST + SSE or keyed WebSocket data, plus the MmflowSocket client.What you can build
Current-state capabilities — everything here ships today.
- React / TypeScript chart components (plus Vue + a framework-agnostic core)
- Bring-your-own-data feeds via createDataFeed / composeFeeds
- Custom indicators in TypeScript via defineIndicator
- Order-flow layers — footprint, order-book heatmap, and trade / whale markers
- Drawing tools — trendlines, levels, channels, Fibonacci
- Read-only market-data APIs — candles, funding, OI, liquidations, whales, options
- Bounded, archive-backed historical context where coverage exists
Capability status
What ships today vs. what's still ahead. Honest by design — no roadmap features dressed up as current ones.
Archives are forward-built and bounded; coverage is source-dependent. Full tick history, historical L2 reconstruction, and durable replay are future infrastructure, not current claims. Packages build dual-format (ESM + CJS) with types and publish through a manual, secret-gated GitHub Actions release workflow.
Quick start
import { Chart } from "@mmflow/react";
import { createMmflowFeed } from "@mmflow/sdk";
import { smaStudy, rsiStudy } from "@mmflow/charts";
<Chart
feed={createMmflowFeed({
apiKey: process.env.NEXT_PUBLIC_MMFLOW_KEY,
transport: "ws",
})}
symbol="BTC"
resolution="1m"
volume
indicators={[smaStudy({ period: 50 }), rsiStudy()]}
/>;REST + SSE are live on Vercel; keyed WebSocket streams run on the branded gateway.