trillium.rs

What it is

Trillium is a modular, async Rust web toolkit built around the idea of “Composition as Configuration”: the components developers choose, and the order in which they compose them, effectively define the application’s configuration. A unified Conn and Handler abstraction runs through request, response, and state handling; loggers, routers, auth gates, and endpoints are all composable Handlers.

Core capabilities

Based on the main text, Trillium offers very broad protocol coverage. Both server and client support HTTP/1.0, HTTP/1.1, HTTP/2, and HTTP/3, along with WebSockets, WebSocket over h2, and WebTransport. It also emphasizes decoupling from runtimes and TLS implementations: developers can choose tokio, smol, async-std, or AWS Lambda, and TLS can be handled via rustls, native-tls, or openssl, while handler code does not need to be aware of these infrastructure differences. Its ecosystem components include Router, Extractor API, sessions, cookies, OpenTelemetry, static files, templates, compression, SSE, channels, reverse proxying, an HTML rewriter, ACME, and an integration testing framework.

Pricing and support

The main text does not disclose an open-source license or pricing model, but it provides links to GitHub, crates.io, docs.rs, and related resources, clearly positioning it for distribution through the Rust crate ecosystem. On the commercial side, the author says Trillium is under active development and that commercial support, architecture reviews, and custom development are available, but no pricing, SLA, or payment methods are listed.

Pros and cons

Its strengths are a unified abstraction model, flexible composition, and the ability to compile only the components you need, avoiding whole-framework lock-in. It also supports multiple runtimes, multiple TLS backends, and multiple HTTP versions, which makes it attractive for infrastructure projects expected to evolve over the long term. The 1.0 release and emphasis on semver also signal API stability. The downsides are that the main text lacks performance benchmarks, production case studies, license information, community size, and details on commercial support; the Rust stack itself also comes with a learning curve.

Who it’s for and access from China

Trillium is suitable for Rust backend teams, services that need newer protocol capabilities such as HTTP/3 or WebTransport, reverse proxy or real-time communication projects, and engineering teams that value testability and modularity. Access from mainland China is not discussed in the main text. GitHub, crates.io, and docs.rs may be affected by local network conditions, so china_access can only be marked as unknown. Alternatives to compare include Axum, Actix Web, Rocket, and Warp.