unnoq

orpc: Build End-to-End Type-Safe APIs

oRPC is a TypeScript toolkit for defining API contracts, implementing server procedures, and calling them with end-to-end type safety. It suits teams building TypeScript APIs that need OpenAPI compatibility and integrations with common frameworks and tools.

View on GitHub Compare
Stars
7
Forks
5
Stars, last 30 days
+3

Our take

Health score

39/100

How it is scored
Activity
52
Community
61
Issues
21
Pull requests
20

+3 stars in the last 30 days

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

10

Forks

5

Change since Nov 16, 2026: 0 stars·0 forks

Overview

oRPC is a TypeScript toolkit for building APIs around shared, typed contracts. It connects contract definition, server implementation, and client calls so API types can flow across those boundaries, reducing the need to maintain separate interface definitions.

It is aimed at TypeScript developers who want contract-first API development alongside RPC-style usage and OpenAPI compatibility. Its package ecosystem also covers schema validators, framework integrations, and supporting features such as rate limiting and tracing.

Key Features

  • Define API contracts as a shared source of truth, then implement them on the server.
  • Consume APIs from clients with end-to-end type safety.
  • Add OpenAPI compatibility and generate contracts from OpenAPI.
  • Convert schemas for Zod, Valibot, and ArkType to JSON Schema.
  • Integrate with frameworks and libraries including Next.js, NestJS, TanStack Query, and SWR.
  • Use built-in packages for publishing, rate limiting, and locking with memory, Redis, and Upstash adapters.
  • Connect observability tools including OpenTelemetry and Pino.

Use Cases

  • TypeScript teams building a new API can use contracts to keep server implementations and client calls aligned.
  • Teams adopting a contract-first workflow can use OpenAPI support and generation to connect API definitions with oRPC.
  • Applications using Zod, Valibot, or ArkType can connect their validation schemas to the toolkit's JSON Schema support.
  • Teams with existing Next.js, NestJS, or TanStack Query applications can use the corresponding integration packages.

Getting Started

Install the packages you need for your API and framework. For example, to add the client package:

npm install @orpc/client

See the oRPC documentation and repository README for setup and package-specific instructions.

Alternatives

  • autobahn-python: Autobahn|Python provides RPC over WebSocket using WAMP in Python, rather than typed TypeScript API contracts and procedures.
ProjectLanguageLicenseStarsStatus
orpcTypeScriptMIT7Not checked yet
autobahn-pythonPython–2.5kActive

Considerations

  • oRPC is a multi-package toolkit, so you will need to choose packages that match your server, client, and integrations.
  • The repository describes some packages as experimental, including integrations for Effect and MSW and the experimental lock package. Check package maturity before relying on them.
  • The repository reports 7 stars, 5 forks, and 1 open issue. These figures provide limited evidence about adoption and maintenance; review the project and its documentation for your requirements.
  • The README links to documentation hosted at orpc.dev and package listings under the @orpc npm scope, while the supplied repository URL is under dinwwwh/orpc. Verify the repository and package sources you intend to use.

Found this useful?

Share it with someone who would like orpc.

Comparisons