Vetis Server is a Rust-focused ecosystem for building lightweight, modular, and high-performance web services. The organization brings together a core HTTP server, runtime adapters, feature crates, templates, and supporting utilities that let developers assemble a stack that matches their runtime and deployment needs.

The projects here are designed to stay small, composable, and fast without sacrificing flexibility. Whether you need a minimal request server, static file serving, proxying, WebSocket support, scripting, or runtime-specific integrations, the Vetis ecosystem is structured to provide the pieces you need.

• vetis — A blazingly fast, minimalist HTTP server built for modern Rust applications.
• vetis-server — Server-side components and supporting modules that complement the core framework.
• vetis-templates — Templates for bootstrapping a Vetis web server project.
• vetis-contrib — Logging, observability, and authentication modules for Vetis applications.

• vetis-tokio — Tokio runtime support for Vetis.
• vetis-compio — Compio runtime support for Vetis.
• vetis-smol — smol runtime support for Vetis.
• vetis-glommio — Glommio runtime support for Vetis.

• vetis-static — Static file serving with caching and multi-runtime support.
• vetis-flash — Fast static-content serving utilities built on top of Vetis.
• vetis-proxy — HTTP proxy support for forwarding requests to upstream services.
• vetis-rev-proxy — Reverse proxy capabilities for Vetis applications.
• vetis-ws — WebSocket support for interactive client-server communication.
• vetis-wt — WebTransport support for modern transport-level features.
• vetis-rhai — Rhai scripting integration for extensibility.

• front — Front-end or application-facing tooling associated with the Vetis ecosystem.

Vetis is built for developers who want:

• small, explicit building blocks instead of heavyweight frameworks
• support for multiple async runtimes without rewriting application code
• modular feature crates that can be added when needed
• a fast path for building web services in Rust

1. Review the core server in vetis.
2. Pick the runtime adapter that matches your stack: vetis-tokio, vetis-compio, vetis-smol, or vetis-glommio.
3. Add the feature modules you need, such as vetis-static, vetis-proxy, or vetis-ws.
4. Use vetis-templates to start new projects with a sensible base.

This organization is open to contributions across the ecosystem. If you want to improve a crate, add a feature, or fix a bug:

• open an issue in the relevant repository
• work from a feature branch
• submit a pull request with a clear explanation and any relevant tests

• .github — GitHub configuration and organization-level community files