oRPC
Typesafe APIs without the framework lock-in
Overview
oRPC solves the type safety gap between frontend and backend without tying you to a specific framework. Define your API procedures with input and output schemas, and oRPC generates a type-safe client automatically. Your frontend code knows exactly what the API expects and returns - at compile time.
Unlike tRPC, oRPC is framework-agnostic and generates OpenAPI specifications from your procedure definitions. This means your API serves both type-safe clients and traditional REST consumers, making it practical for projects that need both internal and external API access.
The contract-first approach lets you define your API surface as a standalone contract, then implement it separately. This separation enables parallel frontend and backend development - the frontend team can build against the contract while the backend team implements it.
Key Features
Type-Safe RPC
End-to-end type safety between client and server
Framework Agnostic
Works with any backend framework - Hono, Express, Fastify
OpenAPI Generation
Automatic OpenAPI spec from procedure definitions
Contract First
Define API contracts separately from implementation
Validation
Zod, Valibot, or ArkType schema validation
Middleware
Composable middleware with typed context propagation
Why We Recommend oRPC
oRPC gives us tRPC-style type safety without the framework coupling. The OpenAPI generation means our APIs serve both internal type-safe clients and external REST consumers from the same code.