tRPC
Hacker ApprovedRanked 3 of 5 rpc frameworks by recommenders
Recommended for end-to-end type safety by sharing TypeScript types between frontend and backend. Main caveat: no spec or schema, so it relies on the type system and ties you to its RPC system.
Recommended for end-to-end type safety by sharing TypeScript types between frontend and backend. Main caveat: no spec or schema, so it relies on the type system and ties you to its RPC system.
14 people gave an opinion
- recommend it
- 12
- criticize it
- 2
- approval share
- 86%
Recommended in 7 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it carries the badge
- 12 people recommend itNeeds 10 or more, met.
- 6 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 7 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
End-to-end type safety
“use something like TRPC to get type inference from your schemas in your route handlers and your front end”
Comment from 4 Dec 2025 in “Anthropic acquires Bun” “funnel all communication with something structured and type safe like tRPC”
Comment from 19 Dec 2025 in “Show HN: I open-sourced my Go and Next B2B SaaS Starter (deploy anywhere, MIT)” “with something like tRPC your data being fully end-to-end typesafe too”
Comment from 1 Apr 2026 in “EmDash – a spiritual successor to WordPress that solves plugin security” - Comment from 9 Jul 2026 in “TypeScript 7”
Shared frontend and backend typings
“there are some amazing new frameworks that reuse typescript types on the server and client (trpc, tanstack)”
Comment from 30 Dec 2025 in “Go Away Python” “use something like TRPC to get type inference from your schemas in your route handlers and your front end”
Comment from 4 Dec 2025 in “Anthropic acquires Bun” “Shared typings between the frontend and backend via tools like tRPC/ oRPC”
Comment from 27 Jan 2026 in “RIP Low-Code 2014-2025” - Comment from 3 Nov 2025 in “Why we migrated from Python to Node.js”
Simpler than GraphQL
“tRPC is a nicer version of client server contracting than graphql in my opinion”
Comment from 14 Dec 2025 in “GraphQL: The enterprise honeymoon is over” “I've switched to primarily using tRPC vs. GraphQL”
Comment from 14 Dec 2025 in “GraphQL: The enterprise honeymoon is over”
What people warn about
Each mark is one comment
No spec; relies on TypeScript types
“tRPC sort of does this (there's no spec, but you don't need a spec because the interface is managed by tRPC on both sides). But it loses the real main defining quality of gql”
Comment from 15 Dec 2025 in “GraphQL: The enterprise honeymoon is over” “Things like tRPC or magic functions are just using Typescript type system and comment to replace the schema”
Comment from 18 Sep 2026 in “Rate limits on GitLab.com are changing”
Other rpc frameworks people recommend
The four most recommended other rpc frameworks, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| gRPC | 25 | 24 | 51% | 8 | — | — |
| ConnectRPC | 15 | 1 | 94% | 5 | — | Approved |
| tRPCThis page | 12 | 2 | 86% | 7 | — | Approved |
| Apache Thrift | 8 | 3 | 73% | 5 | — | — |
| Varlink | 7 | 2 | 78% | 5 | — | — |
What people said
14 of the 15 comments that mention it, newest first. Each links to the original comment.
“zod and tRPC is a lovely combo for building app”
“Things like tRPC or magic functions are just using Typescript type system and comment to replace the schema”
“Nothing can break the type contract anywhere.”
“with something like tRPC your data being fully end-to-end typesafe too”
“they preached tRPC and screamed TYPE SAFETY!!!”
“Shared typings between the frontend and backend via tools like tRPC/ oRPC”
“don't like having to use their RPC system”
“there are some amazing new frameworks that reuse typescript types on the server and client (trpc, tanstack)”
“funnel all communication with something structured and type safe like tRPC”
“tRPC sort of does this (there's no spec, but you don't need a spec because the interface is managed by tRPC on both sides). But it loses the real main defining quality of gql”
“tRPC is a nicer version of client server contracting than graphql in my opinion”
“I've switched to primarily using tRPC vs. GraphQL”
“use something like TRPC to get type inference from your schemas in your route handlers and your front end”
“now my consumers are perfectly typed at dev time”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.