Axion

Axion is the time-series workstation — a desktop-native, AI-native DCC for data that moves through time. You don't run a tool; you compose the procedural machine that visualizes, simulates and predicts, as a versioned node graph with a real compute engine underneath.

It's the application layer of the Axyra stack, and it's domain-agnostic by design: capabilities install as extension packs. Trading is the first pack — not the product. Roughly two-thirds of Axion never mentions a market.

The core idea is that one graph is everything at once: the UI you edit, the compute engine that runs, the editable IR an AI rewrites, and a shareable, versioned asset. Edit it by hand or let a model rewrite it — both touch the same source of truth.

Underneath sits a real engine — vectorized and event-driven from one definition, a Rust cook core for tight loops and a Python sidecar for the heavy and the learned, split automatically and cached by content. Strategies, indicators, models and datasets are content-addressed and reference-tracked. It's local-first and non-custodial: your data and keys never leave the machine unless you send them.

Every project flows through one pipeline: Source → Transform · Model → Simulate → Output. Any time-series comes in — files, APIs, generators, live feeds — runs through a DAG over aligned columns, drives a policy graph for Monte Carlo, sweeps and scenarios, and lands as alerts, webhooks, reports or exports.

Domain packs contribute nodes, panels, providers and run modes behind a stable seam. The trading pack — connectors, an execution router with a risk envelope, a portfolio book — is the proof the seam is real. Audio is the first non-finance vertical; sensors and ops follow.

The web surface is a deep-black marketing sibling of the desktop app's design language. The brand indigo (#818CF8) is the one accent, used sparingly — the 10–20% rule, never as glow or neon. Type is weight-led Geist with a tabular monospace, because numbers are sacred: every figure is tabular, aligned, exact.

The page is built as server components that declare motion intent, with a single GSAP runtime driving scroll reveals, line-draws and parallax, and a code-split Three.js node-network constellation for the hero — gated behind a WebGL and reduced-motion check so it never blocks first paint. A faint blueprint grid and hairline dividers keep it reading like a schematic; motion earns a longer, cinematic tier than the instrument UI's 150ms ceiling.