zoom_in Click to enlarge

Saphir

▲ ▼

language

description Saphir Overview

Saphir is an asynchronous HTTP server framework for the Rust programming language. Its purpose is to give developers structured building blocks for web servers and APIs while retaining relatively low-level control over the web stack, rather than requiring them to assemble every component directly on top of a lower-level library. The framework is aimed at Rust developers who want async request handling, routing, controllers, and related server functionality in one project.

help Saphir FAQ

What is Saphir in Rust?

Saphir is a fully asynchronous HTTP server framework for Rust that aims to provide structured web-server parts without hiding all low-level control. Its documentation positions it as a higher-level layer over libraries such as Hyper. ([Saphir documentation](https://docs.rs/saphir/latest/saphir/))

What web-server pieces does Saphir provide?

The framework includes routing, controllers, handlers, middleware, guards, request and response types, cookies, and multipart support. That gives an API project more structure than assembling every request path directly from a low-level HTTP library.

Can Saphir handle JSON and HTTPS?

Yes, Saphir documents optional features named json, form, validate-requests, and https. The JSON and form wrappers simplify request parsing, while the HTTPS feature provides the pieces needed for encrypted connections.

Does Saphir use Tokio and Hyper?

The documentation for the 3.1.1 crate lists Tokio and Hyper among its dependencies, and its server example uses the Tokio macro runtime. That makes Saphir relevant to Rust developers already working with the Tokio and Hyper ecosystem. ([Saphir crate details](https://docs.rs/crate/saphir/latest))

swap_horiz

Looking for Saphir alternatives? Compare top competitors ranked & scored

arrow_forward