Integrations and bindings

Find an integration or binding

Start with the framework that runs your app, or search for the React library you already use. Framework integrations cover app setup, routing, server rendering, hydration, and builds. Library bindings preserve familiar hooks and components across state, data, routing, UI, forms, charts, 3D, and more.

The directory is server-rendered and its search and filters stay in the URL, so a result from the site search opens the same focused view. Follow a package link for its README. Framework cards also link to the deeper setup guide.

Community bindings

Browse a curated selection of Octane integrations published across the wider ecosystem. Each entry links directly to the project's official documentation; the list is not exhaustive.

Looking for more? Explore community packages that depend on Octane on GitHub. ↗

Install it, then change the import

Install the Octane package instead of the React-facing one:

pnpm add @octanejs/zustand

The library API stays familiar; the import points at its Octane binding:

// React
import { create } from 'zustand';

// Octane
import { create } from '@octanejs/zustand';

From there, use Zustand's store and selector APIs as usual. The same pattern applies to the other bindings: upstream docs teach the library, while the package README records anything Octane-specific.

Check the part you plan to use

Octane and its bindings are beta software. Before building around one, check three things:

1. Is the hook or component you need included?
2. Does a known difference affect your code?
3. If you render on the server, is SSR and hydration covered?

The generated bindings status table answers those questions for all 107 first-party bindings and is checked in CI.