[End User]

Install AXIS, compose source/stream/engine/storage recipes, and run research workflows without a proprietary chart host.

End User

AXIS is an installable charting PWA: load history, stream the present, evaluate Pine Script™ through a pluggable engine, and keep a script library on disk, IndexedDB, cloud, or git. This track is for operators and researchers who use the AXIS—not for plugin authors or Worker deployers.

Language fidelity (grammar, builtins, runtime semantics) lives in PYNE. AXIS never reimplements the language; it hosts evaluation via engine plugins.

Abstract

You compose four axes:

Axis	Question it answers
Source	Where do historical OHLCV bars come from?
Stream	How does the live bar advance?
Engine	Who evaluates the script?
Storage	Where do saved scripts live?

Any lawful combination is valid. Offline lab, desk research against Binance + Flask, AXIS at the edge through a Cloudflare Worker, and a git-backed library are all first-class recipes—see Compose recipes.

Conceptual model

The shell (topbar, chart, editor, results, manager) is AXIS. Calculation is always engine.run({ script, bars, config }). Persistence of scripts is always a storage plugin.

Interface surface

Surface	Role
Topbar	Symbol, interval, source/stream/engine pickers, Load, Run, Live
Watchlist	Quick symbol switch + quote poll
Chart	lightweight-charts panes, drawings, trade markers
Editor	CodeMirror 6 Pine document (docked / popout)
Results	Events, Strategy, Plots, Metrics, Raw + export
Manager	Plugin catalog, URL install, Script Library
Settings	Endpoint, engine, storage, interval defaults

Getting started

Installation — Vite dev, static dist/, or hosted PWA
Quick start — first load + first Run
Compose recipes — offline, desk, multi-venue, CSV, edge, git

Guides

Reference

Glossary
FAQ

Invariants (operator-facing)

AXIS ≠ engine — switching engine does not change the chart library; switching source does not change the language runtime.
Active set is four-tuple — source, stream, engine, storage are selected independently (with sensible defaults when source implies stream).
API keys stay in the browser — cloud storage and Pro keys are not uploaded by the shell except as request headers you configure.
OHLCV bars are not persisted — reload re-fetches history; layout, script draft, and drawings survive in pynescript.axis.v1.