Octane

Neon.Website.Octane packages Octane’s handler and client assets for Node 24 Fetch on Neon Functions. The deployed wrapper does not start a listening Bun server; there is no container or S3 hosting layer.

Prepare the app

Use an existing Octane app or the runnable Octane example. Configure deployment credentials, then install in the app directory:

Install Alchemy and its matching Effect dependencies first; use Node 24 for this build toolchain.

pnpm add -D @alchemy.run/frontend-frameworks @vercel/nft

Select the build adapter

Octane requires the integration’s Node adapter in octane.config.ts. Import it alongside your existing configuration imports:

import { node } from "@alchemy.run/frontend-frameworks/octane/node-adapter";

This adapter emits the portable handler used by the Neon target.

Configure the adapter

export default defineConfig({
  adapter: node(),

Set this instead of a different platform adapter; leave your router configuration in place. RenderRoute and ServerRoute declarations stay in octane.config.ts.

Define the stack

import * as Alchemy from "alchemy";
import * as Neon from "alchemy/Neon";
import * as Effect from "effect/Effect";

export default Alchemy.Stack(
  "NeonOctane",
  { providers: Neon.providers(), state: Alchemy.localState() },
  Effect.gen(function* () {
    const site = yield* Neon.Website.Octane("Web", {
      rootDir: ".",
    });
    return { url: site.url };
  }),
);

The Function serves built client files and forwards application requests to the Octane handler. Server routes can read process.env; public Vite variables are embedded into browser assets, so do not put privileged credentials in them.

Develop and deploy

pnpm exec alchemy dev
pnpm exec alchemy deploy
pnpm exec alchemy destroy

Run separately, destroying when finished. Dev uses Octane’s native Vite server and HMR, returns a local URL, and creates no implicit Project or Function. Append .pipe(Alchemy.remote()) to the Website Effect to use live deployment during dev.

Omitting scope creates an Ohio Project on deploy. Supply either project or branch to reuse a backend; choose Ohio when adding storage. See scope and credentials.