Introduction
MiraServe is a web server and reverse proxy written in Rust, built so that the safe setup is the default one. This page explains what it does, who it is for, and how far along it is.
What MiraServe is
MiraServe serves static sites, forwards requests to application backends (a reverse proxy), and runs PHP sites such as WordPress through a separate PHP-FPM process. You configure it with one file written in KDL, a small, readable configuration language. A minimal production site looks like this:
server {
listen ":443" protocols="h3,h2,h1"
listen ":80" redirect-https=#true
tls {
acme {
email "[email protected]"
challenge "tls-alpn-01"
}
}
}
site "example.com" {
root "/var/www/example"
}
That file gives you HTTPS with certificates from ACME (the protocol Let's Encrypt uses), HTTP/3, HTTP/2 and HTTP/1.1, a redirect from port 80, and strict security headers, all without extra settings.
Who it is for
MiraServe is for administrators who run Nginx, Apache, Caddy or OpenLiteSpeed today and want a server with fewer ways to go wrong. It is also for teams putting AI agents or AI-written sites on the web who want to check who an agent is and limit what it can do.
Main ideas
Memory safety
Every crate uses #![forbid(unsafe_code)], so the compiler rejects code that could touch memory it does not own. unwrap, expect and panic are also forbidden, so bad input becomes an error, not a crash. TLS uses rustls with aws-lc-rs, not OpenSSL.
Modern TLS by default
Only TLS 1.3 is accepted unless you opt a site into TLS 1.2. The key exchange prefers X25519MLKEM768, a classic and post-quantum hybrid that protects recorded traffic against future quantum computers. Private keys can live in a separate signing process, miraserve keyd, so the internet-facing process never holds them. See TLS and certificates.
Confinement
Static files are opened through cap-std, which uses the operating system to refuse any path outside the site root, including symlinks that point elsewhere. On Linux the worker also restricts itself with Landlock (filesystem limits) and seccomp-bpf (system call limits). Plugins run as WebAssembly with fixed memory and CPU budgets. See Sandboxing.
A bridge for existing sites
PHP never runs inside MiraServe. It talks to PHP-FPM over FastCGI, and the wordpress-hardened preset blocks common attack paths such as xmlrpc.php and PHP files in uploads. miraserve import turns an existing Nginx, Apache, Caddy or OpenLiteSpeed config into a draft MiraServe config. See PHP and WordPress and Migrating.
AI-edge features
MiraServe can verify signed requests from AI agents (RFC 9421, Web Bot Auth). It can guard an MCP server (a server that exposes tools to AI agents) and decide per caller which tools may be used. It can also publish signed site releases that switch over atomically and can be rolled back. See MCP gateway and Publishing.
Current status
MiraServe is alpha software, version 0.1.0-alpha.0. It is in private testing and is not available to download yet; the source will be published after testing on real sites and an independent security review. Expect configuration and behaviour to change before then.
Some features are not finished yet:
- Encrypted Client Hello (ECH) is not active, because the TLS library does not yet support it on servers. ECH settings fail validation.
- ACME
dns-01challenges are not supported yet. Usetls-alpn-01orhttp-01. - Landlock and seccomp work only on Linux. On macOS and Windows only the
cap-stdroot confinement applies. - On Windows, MiraServe runs as a Scheduled Task, not a native Windows service. Treat Windows as a development platform for now.
- Apache
.htaccessfiles are not read,mod_phpis not supported, and LiteSpeed LSAPI is not supported. Use PHP-FPM. - WebAssembly plugins cannot make outbound network requests.
Where to go next
- Quickstart: build MiraServe and serve a page locally.
- KDL basics: how the configuration file is written.
- Migrating: move a site from another server.
- Threat model: what MiraServe defends against, and what it does not.