tailcallhq/tailcall
High Performance GraphQL Runtime observed · 2026-08-28
Health v2 · maintenance only
83/100
- Activity 99
- Release rhythm 55
- Longevity 95
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 0
- age_days: 1335
- days_rel: 223
- days_push: 7
- n_releases_24m: 186
Adoption not part of the score
1443 stars · 256 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Tailcall is a high-performance GraphQL runtime written in Rust that lets you build GraphQL backends declaratively by annotating a GraphQL schema with directives like @server and @http, without writing resolver code. It acts as an API orchestration layer and gateway that composes upstream REST, gRPC, and other services into a single GraphQL endpoint.
Use cases
- expose a unified GraphQL API over existing REST microservices
- build a backend-for-frontend layer without writing resolvers
- aggregate multiple upstream APIs into one GraphQL schema
- run a high-performance GraphQL gateway in front of legacy services
- define a GraphQL server entirely from a schema file with no code
- add caching and resiliency to upstream API calls
- replace a hand-written GraphQL server with a declarative config
When to choose
- your data lives in existing REST/gRPC/HTTP APIs you want to expose as GraphQL
- you want schema-first, configuration-driven GraphQL with minimal code
- you need a fast, Rust-based GraphQL gateway or BFF layer
- you want built-in caching, batching, and resiliency for upstream calls
When to avoid
- you need complex custom business logic inside resolvers
- your data sources are databases rather than HTTP/gRPC services
- you already have a mature GraphQL server stack your team knows well
- you need subscriptions or GraphQL features beyond what the runtime supports
Facets
application · maturity active
graphql api-framework http-server api-gateway proxy middleware routing caching web-framework apis backend web-development microservices developer-tools performance rust cli self-hosted cross-platform cloud graphql-runtime backend-for-frontend schema-first declarative-configuration api-orchestration rest-to-graphql grpc no-code-resolvers tailcall docker web-server
8 sources
- readme: https://github.com/tailcallhq/tailcall · fetched 2026-08-28 · e3b9ed231b9f
- homepage: https://tailcall.run · fetched 2026-08-29 · bb88b68e274c
- site_page: https://forgecode.dev/docs · fetched 2026-08-29 · b906d5c4af47
- site_page: https://forgecode.dev/docs/zsh-support · fetched 2026-08-29 · a1fae48eb2a4
- site_page: https://forgecode.dev/docs/forge-services · fetched 2026-08-29 · 21910701fae3
- site_page: https://forgecode.dev/docs/model-selection-guide · fetched 2026-08-29 · 8d1497e1d5b8
- site_page: https://forgecode.dev/docs/operating-agents · fetched 2026-08-29 · 7916af6e4457
- site_page: https://forgecode.dev/releases · fetched 2026-08-29 · 83c629c0e8f1
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| tailcallhq/tailcall | main | 83 |
For agents
markdown · JSON · MCP: product_card(name="tailcallhq/tailcall")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem