Octane is the successor to Inferno, carrying its performance‑first goal forward by compiling React’s hooks, Suspense and actions ahead of time. With Octane there is no virtual DOM, no rules of hooks, and no hand‑maintained dependency arrays—the compiler determines what each effect, memo or callback actually uses, allowing hooks to sit behind conditions or early returns. Improved async starts independent use() calls together, nested fetches warm up early, and streaming SSR sends each boundary as soon as it’s ready.

Templates compile to cloned nodes and direct DOM writes; keyed @for lists move the fewest nodes possible. Plain .tsx still works, so teams can adopt .tsrx one component at a time. Familiar React features—hooks, memo, context, portals, transitions, actions, controlled forms and Suspense—behave exactly as expected, events are native, refs are just props, and 53 first‑party bindings cover state, data, routing, UI, forms, charts, 3D and more. The test suite runs 11,500+ executions across runtime, compiler, SSR and bindings, with 3,900+ distinct cases, ensuring React‑derived coverage is tracked case by case.

Migration is incremental: existing TSX can stay, while new components are written in .tsrx. Octane Compat lets you drop compiled Octane islands into a React 19 app, preserving native events, real React context, SSR and hydration without a rewrite. The model keeps components as plain functions that read top‑to‑bottom, so AI agents can migrate apps without redesigning around a new reactive model. Performance suites show Octane matching or exceeding baseline 1×, proving fast feels natural, not a new way of thinking.