Skip to content
djust/docs
Appearance
Mode
djust.org →

v0.9.0 · The headline

Server actions in Python.

React 19 mental model — without the React.

Decorate a method with @action. The template gets pending, error, and result for free. No useState, no setLoading, no API client, no JSON contract you maintain twice. The submit button disables itself; the spinner shows; the error renders — zero per-handler wiring.

§ I

React 19 ergonomics, in Python.

Every reactive primitive React 19 ships, plus the bits Phoenix LiveView taught the industry — and you write Python with HTML templates. No client framework. No JSON contract to maintain on both sides.

§ II

Real-time without a JavaScript framework.

Pushes from the database, from a worker, from a webhook — all land in the connected user's open page in ~50ms. Same template, same Python view, same auth. No Celery for fanout, no Redis for pub/sub, no second service to operate.

§ III

Production-grade developer experience.

The boring-but-load-bearing parts that decide whether a framework survives a real team for a year. Hot reload that keeps form input. Type-checked templates. Time-travel debugging with branched timelines. A real error overlay. 60+ system checks at startup.

§ Why

Seven convictions, in one stack.

  1. 01

    Complexity is the enemy.

    No build step in user projects. No node_modules. A single readable client. Every layer of complexity removed is a bug that won't exist.

  2. 02

    Developer first.

    WebSockets, VDOM, reconnection, security — all handled. Clear errors. System checks at startup. You write app logic, not infrastructure.

  3. 03

    AI-ready by design.

    Less surface area means generated code can be trusted on the boring parts. The AI doesn't write your auth, state, or API contracts.

  4. 04

    One stack, one truth.

    No API layer. No frontend / backend split. One Python codebase, one deploy, one stack trace.

  5. 05

    Performance is architecture.

    Rust for the VDOM and template engine isn't premature optimization — it's the right tool for that layer of the stack.

  6. 06

    Own your stack.

    Single readable client.js. No npm registry to trust. MIT licensed. The code you ship is the code you can read.

  7. 07

    Opinionated where it matters.

    Strong opinions on security, state, transport. Zero opinions on CSS, markup, design. Bring your own everything visual.

§ Index Or browse every release-noted feature (616) 219 user-facing · 102 reference · 295 internal · 63 releases