- Website
- orpc.dev
- Social media
- @middleapi
About oRPC
oRPC lets you define your API once and generates a fully typed client, a REST API with an OpenAPI document, and typed realtime streams. It’s built for backend and frontend teams who want end-to-end type safety without code generation or runtime lock-in.
Key Features
When you design around a contract, you get a single source of truth that covers client, server, and docs, with errors and middleware wired in from the start:
Typed client
The client interface mirrors the server router, carrying input/output shapes and error contracts without any code generation; your types flow directly from handlers to the client.
Contract-first, typed errors
declare inputs, outputs, and error variants in one place; at runtime the client sees declared error codes and associated data, and you can handle them statically.
REST + OpenAPI
OpenAPI document is generated automatically and kept in sync with the router; REST endpoints mirror procedures for easy HTTP access.
Middleware and in-context typing
middleware can inject typed context (like auth) and guards; the server and client share types, with compile-time checks ensuring consistency.
Summary
Best for backend teams building internal APIs, frontend teams consuming typed clients, and platform teams exposing services via REST and OpenAPI.
