tako
A pragmatic Rust framework for building cohesive network services across HTTP, WebSocket, gRPC, TCP, UDP, and Unix sockets.
What is tako?
Tako is a lightweight and extensible Rust web framework built on Tokio and Hyper, designed for services that go beyond plain HTTP. It enables developers to build one cohesive application across multiple transports like HTTP, WebSocket, gRPC, TCP, UDP, and Unix sockets with a single routing, middleware, and observability model. The framework addresses the complexity of gluing together multiple libraries for different protocols, offering a unified solution for modern network services.
Rust developers building API backends, realtime applications, protocol gateways, internal platforms, telemetry collectors, control planes, or edge-facing services that require support for multiple communication protocols.
Developers choose Tako for its pragmatic, all-in-one approach to multi-transport services, eliminating the need to integrate and maintain several partially overlapping libraries. Its dual runtime support (Tokio/Compio), built-in platform primitives, and extensive middleware ecosystem provide a coherent and ergonomic development experience without sacrificing performance.
Overview
Tako is a lightweight and minimalistic web framework built on Tokio and Hyper written in Rust.
Use Cases
Best For
- Building API backends that also require WebSocket or SSE for realtime features
- Developing protocol gateways that need to handle HTTP, gRPC, and raw TCP/UDP traffic
- Creating internal platforms or control planes with unified observability across transports
- Implementing edge-facing services that leverage HTTP/3 (QUIC) and WebTransport
- Consolidating multiple protocol libraries into a single, maintainable codebase
- Building realtime coordination systems with built-in signals, queues, and streaming primitives
Not Ideal For
- Projects exclusively requiring simple HTTP REST APIs without real-time or multi-protocol needs
- Teams needing full HTTP/3 and gRPC support on the Compio async runtime
- Developers preferring minimal, opinionated frameworks with a larger ecosystem and community
Pros & Cons
Pros
Enables serving HTTP, WebSocket, gRPC, TCP, UDP, and Unix sockets from a single application, reducing the complexity of integrating multiple libraries.
Offers first-class support for both Tokio and Compio, allowing developers to choose the runtime based on deployment constraints without changing the framework API.
Includes middleware for authentication, rate limiting, compression, and observability, minimizing external dependencies for common service requirements.
Provides optional SIMD JSON parsing, zero-copy extractors, and jemalloc support, as highlighted in benchmarks showing throughput comparable to Axum.
Cons
Many advanced features like HTTP/3, gRPC, and SIMD parsing require enabling specific flags, which can complicate configuration and increase build overhead.
Protocols such as HTTP/3, WebTransport, and gRPC are not fully supported on the Compio runtime, limiting portability for QUIC-based workloads.
The project is pre-v1.0.0, indicating potential API instability and a smaller ecosystem compared to mature frameworks like Axum or Actix.
Frequently Asked Questions
Related Projects
tokio/axumHTTP routing and request-handling library for Rust that focuses on ergonomics and modularity
RocketA web framework for Rust.
actix-webActix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
LeptosBuild fast web applications with Rust.
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.