Memory corruption bugs
Buffer overflows and use-after-free are ruled out: pure Rust with unsafe code forbidden.
MiraServe is a memory-safe, secure web server and edge gateway written in Rust, with post-quantum HTTPS and AI-native protection built in. Every request is checked at the edge before it reaches your site.
Most sites still run on servers designed decades ago, with security bolted on afterwards. MiraServe starts from safe defaults.
Crawlers, AI agents and MCP tools are a growing share of web traffic, and anyone can fake a user-agent. MiraServe checks identity cryptographically and applies policy at the edge.
GET /pricing HTTP/3
Host: shop.example.com
GET /docs/install HTTP/2
Accept: text/markdown
Signature-Agent: "https://agent.example"
Signature-Input: sig1=("@authority" "signature-agent")…
GET /wp-login.php HTTP/1.1
User-Agent: ExampleAIBot/1.0
POST / HTTP/1.1
Content-Length: 44
Transfer-Encoding: chunked
POST /mcp HTTP/2
{"method":"tools/call","params":{"name":"delete_user"}}
RFC 9421 signatures prove an AI agent is who it says it is.
OAuth metadata, per-tool access control and redacted audit logs.
AI-written sites are scanned for secrets, inline script and CSP issues, then swapped in atomically.
llms.txt, Markdown negotiation and zero-buffer streaming for LLM endpoints.
Each threat below is handled in the server itself, with no extra add-ons to install.
Buffer overflows and use-after-free are ruled out: pure Rust with unsafe code forbidden.
An RFC 9110/9112 normaliser rejects ambiguous message framing before routing.
HTTP/2 and HTTP/3 flood guards, slow-body limits and a bounded-memory GCRA rate limiter.
Files are opened beneath the web root only, enforced by the kernel (openat2 RESOLVE_BENEATH).
In split-daemon mode private keys live in the separate miraserve-keyd daemon, never in worker memory.
Post-quantum hybrid key exchange (X25519MLKEM768) protects traffic recorded today.
miraserve check --strict audits a config for security mistakes before the server will run it.
WebAssembly plugins run with CPU, memory and time limits and no file, environment or network access.
PHP runs outside the server process over FastCGI, with HTTPoxy protection and a hardened WordPress preset.
Published sites are checked for secrets, inline script and CSP problems before they go live.
Unsigned bots claiming to be AI agents are throttled, challenged or blocked by policy.
MCP tool calls are checked against allow and deny lists, with size limits and audit logs that redact secrets.
Import your existing config as a draft, audit it, and run it with TLS 1.3, post-quantum key exchange and HTTP/3 switched on.
Sandboxed wasi:http plugins, the miraserve-keyd signing daemon, ECH key tooling, and Prometheus plus OTLP export.
Signed site bundles with instant rollback, Web Bot Auth verification and the MCP security gateway.
Request-smuggling defences, rate limiting, WordPress hosting over FastCGI, and miraserve import.
MiraServe is being tested privately before anyone else runs it. The source code will be published after testing on real sites and an independent security review.