Skip to content
You are reading the v2 docs, currently in beta.V1 docs
oRPC
Esc
↑↓navigate↵open⌘Jpreview
On this page

Adapters

Pick the oRPC adapter for your runtime, framework, or messaging channel, from the Fetch API and Node HTTP to Next.js, Hono, WebSocket, and Electron.

An adapter connects a handler to where your code runs. The router stays the same, so switching hosts only changes the few lines that mount the handler. HTTP adapters serve both the RPC Handler and the OpenAPI Handler.

Core

  • Fetch API: Bun, Deno, and anything built on Request and Response.
  • Node HTTP: Node’s http, https, and http2 servers.
  • Fastify: Fastify servers.
  • AWS Lambda: API Gateway and Function URLs, with response streaming.
  • WebSocket: ws, crossws, Bun, Deno, Cloudflare, and uWebSockets.
  • Message Port: iframes, workers, and other contexts linked by a MessagePort.

Frameworks

Built on the Fetch API: Next.js, Nuxt, SvelteKit, TanStack Start, SolidStart, React Router, Astro, Hono, Elysia, and H3. Built on Node HTTP: Express.js.

Platforms

  • Cloudflare Workers: the Fetch API Adapter plus the compatibility flags it needs.
  • Expo: call oRPC from a React Native app.

Between Contexts

Built on the Message Port Adapter: Browser (extensions and windows), Electron, Web Workers, and Worker Threads.

Last updated on

Was this page helpful?