# The creator of mod_wsgi returns with Muru, an AI-assisted Rust server for Python apps

Original title: Muru – AI-assisted Rust server for Python apps by mod_WSGI's creator

> Hacker News story 50597959 · language: en · submitted 2026-11-22
> Web version: https://zeli.app/story/50597959
> About this feed: https://zeli.app/llms.txt · Agent guide: https://zeli.app/skill.md

▲ 65 · by [joshcsimmons](<https://news.ycombinator.com/user?id=joshcsimmons>) · 💬 10
[original](<https://simonwillison.net/2026/Nov/21/muru/>) · [HN discussion](<https://news.ycombinator.com/item?id=50597959>)

## Summary

Twenty years after starting mod_wsgi, Graham Dumpleton is building Muru, an AI-assisted Rust server for running ASGI and WSGI Python apps in development and production. He has published a detailed series of posts tracing the project's development, covering worker internals, import-once-fork-many, HTTPS in development, canary releases without a service mesh, scaling to zero, and a toolbar with tracing on every page.

## Key quote

> The AI may be doing a lot of the work on the surface, but deciding what isn't good enough yet is still down to me, and twenty years of getting things wrong with mod_wsgi turns out to be useful for that.

## HN discussion (10 comments)

### [d1l](<https://news.ycombinator.com/item?id=50600725>)

> I respect Graham and recognize how important mod_wsgi was, we ran it back at my first python job. That said the posts read like they were mostly AI generated and feel dead and without value. They seem designed to serve a purpose but feel clumsy and soulless to me.

### [ptx](<https://news.ycombinator.com/item?id=50600505>)

> The LLM-generated writing is incredibly tedious to read, but I like the idea of pre-loading the application and then forking the workers (kind of like Android's Zygote), while, as the LLM puts it, "Muru also takes care to freeze the garbage collector's view of the preloaded objects before forking", or, as it's more concisely put in the code, "gc.freeze()".
>
> A variation on that theme that I would like to try is forking a worker per user (or per session), which would be sandboxed (e.g. with Capsicum in FreeBSD) and only have access to that user's credentials. A separate process would route requests to these per-user workers and provide them with the appropriate credentials. This could then be combined with PostgreSQL's row-level security, with each user having their own user in PostgreSQL, and the per-user worker only having access to that particular user's database credentials.
>
> I feel like this should significantly limit the consequences of both SQL injection vulnerabilities and RCE vulnerabilities. It wouldn't solve stored XSS, I suppose, but I believe that is handled by using a template language for HTML (one that encodes parameters automatically on output). It also probably wouldn't scale to a planet-scale mass-market web application, but there are lots of apps that don't need that kind of scale but do need to be secure.
>
> Maybe this sort of thing has already been done and written about (by humans)?

### [sheepscreek](<https://news.ycombinator.com/item?id=50600162>)

> \> The AI may be doing a lot of the work on the surface, but deciding what isn't good enough yet is still down to me...
>
> We've gone from talking about giving agency to AI (agents) to us having some agency over them.
>
> How the turn tables!

---

## Cite

- Page: https://zeli.app/story/50597959
- Date: 2026-11-22
- Source: simonwillison.net (https://simonwillison.net/2026/Nov/21/muru/)
- Hacker News: https://news.ycombinator.com/item?id=50597959

## Other languages

- zh: https://zeli.app/zh/story/50597959 · markdown: https://zeli.app/zh/story/50597959.md
- ja: https://zeli.app/ja/story/50597959 · markdown: https://zeli.app/ja/story/50597959.md
- ko: https://zeli.app/ko/story/50597959 · markdown: https://zeli.app/ko/story/50597959.md
- de: https://zeli.app/de/story/50597959 · markdown: https://zeli.app/de/story/50597959.md
- es: https://zeli.app/es/story/50597959 · markdown: https://zeli.app/es/story/50597959.md
- ru: https://zeli.app/ru/story/50597959 · markdown: https://zeli.app/ru/story/50597959.md
