---
title: 'oRPC vs tRPC vs Hono'
description: 'See how oRPC compares to tRPC and Hono across type safety, OpenAPI support, framework integrations, and runtime performance.'
sidebar:
  label: 'Comparison'
  icon: scale
---

oRPC, [tRPC](https://trpc.io/), and [Hono](https://hono.dev/) all deliver end-to-end typesafe APIs in TypeScript, but they take different approaches. tRPC focuses on RPC for full-stack TypeScript apps, Hono is a general-purpose web framework with an RPC feature, and oRPC combines typesafe RPC with first-class OpenAPI support.

## Features

- ✅ First-class, built-in support
- 🟡 Lacks features or requires third-party integrations
- 🛑 Not supported or not documented

Checked against tRPC 11.29 and Hono 4.13 (November 2026).

### Type Safety

| Feature                                                                                        | oRPC | tRPC | Hono |
| ---------------------------------------------------------------------------------------------- | ---- | ---- | ---- |
| End-to-end typesafe input/output                                                               | ✅   | ✅   | ✅   |
| [End-to-end typesafe errors](/docs/client/error-handling)                                      | ✅   | ✅   | ✅   |
| [End-to-end typesafe File/Blob](/docs/binary-data)                                             | ✅   | 🟡   | 🟡   |
| [End-to-end typesafe Server-Sent Events](/docs/async-iterator-object)                          | ✅   | ✅   | 🛑   |
| [End-to-end typesafe `ReadableStream<Uint8Array>`](/docs/binary-data#readablestreamuint8array) | ✅   | 🛑   | 🛑   |
| [Typesafe at scale](#type-checking-performance)                                                | ✅   | ✅   | 🛑   |

oRPC types errors per procedure or globally: throw a plain `ORPCError`, [declare errors](/docs/error-handling) with a schema for each code's data on a single procedure or a shared builder, or define them once and reuse them everywhere via an [error factory](/docs/error-handling#error-factory). oRPC is also the only one that types binary data in both directions.

### API Design & OpenAPI

| Feature                                                                              | oRPC | tRPC | Hono |
| ------------------------------------------------------------------------------------ | ---- | ---- | ---- |
| Implementation-first approach                                                        | ✅   | ✅   | ✅   |
| [Contract-first approach](/docs/contract-first)                                      | ✅   | 🛑   | 🟡   |
| [OpenAPI spec generation](/docs/openapi/specification)                               | ✅   | 🟡   | 🟡   |
| [Standard Schema (Zod, Valibot, ArkType, ...)](/docs/integrations/standard-schema)   | ✅   | ✅   | 🟡   |
| [Native types (Date, URL, Set, Map, ...)](/docs/rpc/serializer#supported-data-types) | ✅   | 🟡   | 🛑   |
| [Custom serializers](/docs/rpc/serializer#custom-serializers)                        | ✅   | ✅   | 🛑   |
| [Bracket notation](/docs/openapi/bracket-notation)                                   | ✅   | 🛑   | 🛑   |
| [Lazy router (code splitting, faster cold starts)](/docs/router#lazy-router)         | ✅   | ✅   | 🛑   |

oRPC serves the same procedures over its [RPC protocol](/docs/rpc/protocol) and RESTful [OpenAPI endpoints](/docs/openapi/handler), and generates the spec with a first-party package. Native types like `Date` or `Map` work out of the box.

### Integrations & Ecosystem

| Feature                                                                                       | oRPC | tRPC | Hono |
| --------------------------------------------------------------------------------------------- | ---- | ---- | ---- |
| [WebSockets](/docs/adapters/websocket)                                                        | ✅   | ✅   | 🟡   |
| [Hibernation APIs (Cloudflare WebSocket Hibernation, ...)](/docs/integrations/hibernation)    | ✅   | 🛑   | 🛑   |
| [Message Port (Electron, browser extensions, workers, ...)](/docs/adapters/message-port)      | ✅   | 🟡   | 🛑   |
| [Batch requests](/docs/plugins/batch)                                                         | ✅   | ✅   | 🛑   |
| [Pub/Sub publisher (Redis, Upstash, Durable Objects, ...)](/docs/helpers/publisher)           | ✅   | 🟡   | 🛑   |
| [Rate limiting (Redis, Upstash, Cloudflare, ...)](/docs/helpers/ratelimit)                    | ✅   | 🛑   | 🟡   |
| [Locking (Redis, Upstash, Durable Objects, ...)](/docs/helpers/lock)                          | ✅   | 🛑   | 🛑   |
| [Client plugins and interceptors](/docs/rpc/link)                                             | ✅   | ✅   | 🛑   |
| [TanStack Query integration (React)](/docs/integrations/tanstack-query)                       | ✅   | ✅   | 🟡   |
| [TanStack Query integration (Vue, Solid, Svelte, Angular)](/docs/integrations/tanstack-query) | ✅   | 🟡   | 🛑   |
| [SWR and Pinia Colada integrations](/docs/integrations/swr)                                   | ✅   | 🟡   | 🟡   |
| [AI SDK integration](/docs/integrations/ai-sdk)                                               | ✅   | 🛑   | 🛑   |
| [MCP integration (procedures as AI agent tools)](/docs/integrations/mcp)                      | ✅   | 🟡   | 🟡   |
| [Next.js Server Actions support](/docs/integrations/next)                                     | ✅   | ✅   | 🛑   |
| [Built-in plugins (CORS, CSRF, Retry, ...)](/docs/plugins/cors)                               | ✅   | 🟡   | ✅   |
| [Built-in helpers (cookie, encryption, signing, ...)](/docs/helpers/cookie)                   | ✅   | 🛑   | ✅   |
| [NestJS integration](/docs/integrations/nest)                                                 | ✅   | 🟡   | 🛑   |
| [OpenTelemetry integration](/docs/integrations/opentelemetry)                                 | ✅   | 🛑   | 🟡   |
| [Cloudflare Workers Traces integration](/docs/integrations/cloudflare-traces)                 | ✅   | 🛑   | 🛑   |

Every oRPC integration above is first-party.

:::info
Coming from tRPC? Follow the [migration guide](/docs/migrations/from-trpc), or [use both together](/docs/integrations/trpc) during a gradual migration.
:::

## Performance

:::warning
Treat these numbers as reference measurements, not a reason to switch frameworks. All three are fast enough for production. The per-request difference is tiny next to your business logic, database, and network, and results vary across environments and workloads.
:::

All numbers come from the [middleapi/orpc-benchmarks](https://github.com/middleapi/orpc-benchmarks) run of November 17, 2026, with oRPC 2.0.0-beta.51, tRPC 11.28.3, and Hono 4.13.19 on Node.js 26.13.1. Each server runs on its own dedicated CPU of a 4-vCPU cloud VM, so the results are single-core throughput. Handlers are no-ops with pass-through validation, so the results measure framework overhead only. Every response carries a `Date`, so each library's serializer runs on every request.

### Throughput

Median requests per second over 10 rounds, each on a fresh server after a warm-up, with 10 connections that each keep one request in flight:

| Scenario                            | oRPC   | tRPC   | Hono   |
| ----------------------------------- | ------ | ------ | ------ |
| RPC over HTTP (req/s)               | 28,118 | 6,976  | n/a    |
| RPC over WebSocket (req/s)          | 27,448 | 21,095 | n/a    |
| OpenAPI (RESTful) over HTTP (req/s) | 28,167 | n/a    | 25,410 |

oRPC handles about 4.0x as many requests as tRPC over HTTP and 1.3x over WebSocket. oRPC and Hono are close on RESTful throughput: oRPC is about 11% ahead, which is within the run's noise. Throughput on a cloud VM drifts over the day: in repeated runs on the same VM type, the RPC-over-HTTP ratio ranged from 3.6x to 4.4x, so only compare numbers from the same run.

### Server Cost and Latency

The same rounds also record server CPU time per request, peak memory, and latency:

| Run                       | CPU / request | Peak RSS | Latency p50 | Latency p99 |
| ------------------------- | ------------- | -------- | ----------- | ----------- |
| RPC over HTTP · oRPC      | 35.0 µs       | 88 MiB   | 0.31 ms     | 0.86 ms     |
| RPC over HTTP · tRPC      | 141.3 µs      | 318 MiB  | 1.11 ms     | 5.57 ms     |
| RPC over WebSocket · oRPC | 35.4 µs       | 115 MiB  | 0.31 ms     | 1.01 ms     |
| RPC over WebSocket · tRPC | 46.7 µs       | 84 MiB   | 0.40 ms     | 1.17 ms     |
| OpenAPI over HTTP · oRPC  | 34.9 µs       | 89 MiB   | 0.31 ms     | 0.89 ms     |
| OpenAPI over HTTP · Hono  | 38.4 µs       | 94 MiB   | 0.34 ms     | 0.94 ms     |

Over HTTP, oRPC needs about a quarter of tRPC's CPU time per request. oRPC and Hono are within about 10% of each other on every metric.

### Clinic Doctor Profiles

Every server is also profiled with [Clinic.js Doctor](https://clinicjs.org/doctor/) under the same load. Each profile is a single round, so compare behavior, not throughput:

| Run                       | CPU (avg) | Memory (RSS) | Event loop delay (avg) | Other detected issues | Full report                                                                                                                                             |
| ------------------------- | --------- | ------------ | ---------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| RPC over HTTP · oRPC      | 98%       | 80-97 MiB    | 0.06 ms                | none                  | [view](https://htmlpreview.github.io/?https://github.com/middleapi/orpc-benchmarks/blob/main/benchmarks/rpc-orpc/.clinic/report.clinic-doctor.html)     |
| RPC over HTTP · tRPC      | 99%       | 76-249 MiB   | 0.86 ms                | memory: heapUsed      | [view](https://htmlpreview.github.io/?https://github.com/middleapi/orpc-benchmarks/blob/main/benchmarks/rpc-trpc/.clinic/report.clinic-doctor.html)     |
| RPC over WebSocket · oRPC | 97%       | 74-116 MiB   | 0.08 ms                | cpu: data             | [view](https://htmlpreview.github.io/?https://github.com/middleapi/orpc-benchmarks/blob/main/benchmarks/ws-orpc/.clinic/report.clinic-doctor.html)      |
| RPC over WebSocket · tRPC | 98%       | 75-93 MiB    | 0.07 ms                | none                  | [view](https://htmlpreview.github.io/?https://github.com/middleapi/orpc-benchmarks/blob/main/benchmarks/ws-trpc/.clinic/report.clinic-doctor.html)      |
| OpenAPI over HTTP · oRPC  | 98%       | 78-93 MiB    | 0.08 ms                | none                  | [view](https://htmlpreview.github.io/?https://github.com/middleapi/orpc-benchmarks/blob/main/benchmarks/openapi-orpc/.clinic/report.clinic-doctor.html) |
| OpenAPI over HTTP · Hono  | 99%       | 73-98 MiB    | 0.10 ms                | none                  | [view](https://htmlpreview.github.io/?https://github.com/middleapi/orpc-benchmarks/blob/main/benchmarks/openapi-hono/.clinic/report.clinic-doctor.html) |

Every server is saturated, so Doctor flags event loop utilization on every run. That is expected under this load and left out of the table. The `cpu: data` flag on oRPC's WebSocket run means Doctor's CPU model could not settle on the samples, not a performance issue.

### Type-Checking Performance

On a large, fully typed project with 3,000 procedures across 1,501 routers and a typed client call for every procedure, checked with TypeScript 7.0.2 (`tsc --singleThreaded`), median of 30 rounds:

| Metric         | oRPC    | tRPC      |
| -------------- | ------- | --------- |
| Check time     | 1.59 s  | 1.97 s    |
| Total time     | 1.81 s  | 2.13 s    |
| Types          | 204,344 | 223,766   |
| Instantiations | 775,928 | 1,043,234 |
| Memory used    | 241 MiB | 224 MiB   |

oRPC needs about 26% fewer type instantiations and 9% fewer types. Unlike timings, these counts are deterministic and comparable across machines. The check-time gap is within noise.

Hono has no column because its RPC types hit [known limits](https://hono.dev/docs/guides/rpc#known-issues) well before this size.

### Bundle Size

Bundle sizes for a minimal client and server pair, measured with the same versions. tRPC includes `superjson` to match oRPC's built-in native types, and Hono includes `@hono/node-server` to match the Node.js servers in the other bundles.

| Metric          | oRPC    | tRPC    | Hono    |
| --------------- | ------- | ------- | ------- |
| Minified        | 49.2 kB | 79.1 kB | 48.1 kB |
| Minified + gzip | 15.9 kB | 25.8 kB | 18.1 kB |

Measure yourself: [oRPC](https://bundlejs.com/?q=%40orpc%2Fclient%402.0.0-beta.51%2C%40orpc%2Fclient%402.0.0-beta.51%2Ffetch%2C%40orpc%2Fserver%402.0.0-beta.51%2C%40orpc%2Fserver%402.0.0-beta.51%2Fnode&treeshake=%5B%7B+createORPCClient+%7D%5D%2C%5B%7B+RPCLink+%7D%5D%2C%5B%7B+os+%7D%5D%2C%5B%7B+RPCHandler+%7D%5D) · [tRPC](https://bundlejs.com/?q=%40trpc%2Fclient%4011.28.3%2C%40trpc%2Fserver%4011.28.3%2C%40trpc%2Fserver%4011.28.3%2Fadapters%2Fstandalone%2Csuperjson%402.2.6&treeshake=%5B%7B+createTRPCClient%2ChttpLink%2ChttpSubscriptionLink%2CsplitLink+%7D%5D%2C%5B%7B+initTRPC+%7D%5D%2C%5B%7B+createHTTPServer+%7D%5D%2C%5B%7B+default+as+SuperJSON+%7D%5D) · [Hono](https://bundlejs.com/?q=hono%404.13.19%2Chono%404.13.19%2Fclient%2C%40hono%2Fnode-server%402.1.9&treeshake=%5B%7B+Hono+%7D%5D%2C%5B%7B+hc+%7D%5D%2C%5B%7B+serve+%7D%5D)
