FAQ

A web framework for Rust. Files are routes, .wisp templates compile to Rust, forms post to actions, and the app ships as one binary. Start with Why Wisp or the Quick Start.

Yes. Route logic, actions and models are Rust. The templates read like HTML, and the compiler infers most types, so app code stays short.

Templates and routes compile to Rust, so a request runs plain compiled code. The I/O drivers answer most requests without waking a task, and a route pays only for the features it uses. Benchmarks has the details.

It aims at the same job, with file routes, form actions and server rendering, in Rust. The measured gaps are in speed (Benchmarks) and in tokens (Tokens).

Yes. A form posts to its action and the server answers with HTML. With JavaScript on, the page updates in place. Components ship no JavaScript unless you add some.

Anywhere a binary runs, in a container, as static HTML, or built for Cloudflare, Deno, Vercel, Netlify, Node, Bun or Lambda. See Deploying.

Wisp gives tools, not services: a table type that keeps rows in log files or any database, sessions, password hashing, signed tokens and OAuth helpers. See Data and Auth.

Not outside the Linux I/O drivers and the edge exports. See Security and Hardening.

wisp lsp powers a VS Code extension, and there is support for Zed, tree-sitter and Prettier. See Design Tooling.

AGENTS.md is the whole reference in one file, and wisp mcp serves the docs over MCP: claude mcp add wisp -- wisp mcp.

On Community: the Discord, GitHub Discussions and the issue trackers.