A cross-platform, high-performance asynchronous web server for serving static files, built with Rust.
Static Web Server is a lightweight, high-performance web server built with Rust specifically for serving static files and assets. It solves the need for a fast, secure, and easy-to-deploy static file server that minimizes resource overhead while providing production-ready features like compression, HTTP/2, and monitoring. It is designed to be cross-platform and runs as a tiny standalone binary.
Developers and system administrators who need a reliable, performant static file server for hosting websites, single-page applications, or assets in production or development environments.
Developers choose Static Web Server for its exceptional speed, minimal footprint, and robust feature set—all in a memory-safe, dependency-free binary. It outperforms many alternatives in benchmarks while offering advanced capabilities like compression, security headers, and Prometheus metrics out of the box.
A cross-platform, high-performance and asynchronous web server for static files-serving. ⚡
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Leverages Hyper and Tokio for asynchronous networking, consistently outperforming alternatives in benchmarks as shown in the project's repository.
Single ~4MB static binary with no external dependencies, perfect for minimal Docker images and resource-constrained environments.
Supports GZip, Brotli, Zstandard compression on-demand and Cache-Control headers, optimizing asset delivery and reducing bandwidth.
Includes security headers, graceful shutdown, and HTTP/2 with TLS, ensuring safe and reliable operation in production settings.
Configurable via CLI, environment variables, or TOML file, with features like directory listing, CORS, and custom error pages for tailored deployments.
Cannot serve dynamic content or handle server-side logic, requiring separate services for applications beyond static file hosting.
While TLS is supported, users must manually manage SSL certificates, missing out-of-the-box integration with services like Let's Encrypt.
TOML files and glob pattern matching for headers and redirects can be complex for users accustomed to simpler configuration formats.