Autumn 0.7.0

Ship the app, not the plumbing.

Autumn gives Rust teams the batteries they expect from mature app frameworks: typed routes, Maud views, Postgres persistence, background work, health checks, and production defaults in one server-rendered path.

Get started Read the docs

Rust

use autumn_web::prelude::*;

#[get("/")]
async fn index() -> Markup {
    html! { h1 { "Hello, Autumn." } }
}

#[autumn_web::main]
async fn main() {
    autumn_web::app()
        .routes(routes![index])
        .run()
        .await;
}

Companion release

Autumn Harvest 0.6.0

Harvest adds Postgres-backed durable workflows to Autumn: activities, timers, signals, child workflows, DAG schedules, replay, dead letters, and a management API without operating a separate workflow server.

Read Harvest overview Guide API docs Crate

Start with intent

Pick your entry point

Build first

Getting Started with Autumn

This guide takes you from an empty directory to a running Autumn application with routes, a Postgres-backed model, HTML templates, styling, and interactivity. Budget about 30 minutes.

Read guide Map what you know

Coming From Other Frameworks

If you think in Spring Boot, Django, or Rails, this guide maps the concepts you already know to their Autumn equivalents. Same ideas, different syntax.

Read guide

Core workflows

Build, test, secure, and deploy

What Happens When...The questions you have at hour two, not hour one. This guide covers the failure modes, edge cases, and "what if" scenarios that the getting-started guide doesn't cover.Integration TestingAutumn ships a first-party test surface (autumn_web::test) that brings Rails-grade ergonomics to Rust integration testing: one line to boot a fully-wired app, assertions that chain, and a shared Postgres testcontainer that keeps your test suite fast.Record-Level Authorization#[secured] answers "are you in?" — is this request authenticated, and is the user in one of the listed roles? It does not answer "are you allowed to act on this specific record?" That is the question every multi-user CRUD app has to answer at every write endpoint, and it is what Autumn's Policy trait, the #[authorize] macro, and the policy = argument on #[repository] exist for.Background Jobs (`#[job]`)Autumn provides first-class ad-hoc background jobs for request-triggered async work.Cloud-Native AutumnThis guide is the blunt version: Autumn can run as a single-process monolith with almost no config, but that does not automatically make every default safe for multi-replica production.Deploying an Autumn AppThis guide walks you from a fresh autumn new project to a production-shaped container running against a real Postgres database. Every command is verbatim; no file editing is required to reach a running container.

For coding agents

Point your agent at these docs

This site serves its own guides over the Model Context Protocol at https://autumn-web.app/mcp. Any MCP-capable coding agent can search the guides and read them as Markdown, so it answers from the Autumn 0.7.0 docs that are deployed rather than from whatever it remembers. No key, no account — it is a public read-only endpoint.

An agent that does not speak MCP can ask any page here for its Markdown instead of scraping the HTML: send Accept: text/markdown and the same URL answers with the guide's source.

Shell

claude mcp add --transport http autumn-docs \
  https://autumn-web.app/mcp

# or, in an MCP client's config file:
{ "mcpServers": {
    "autumn-docs": {
      "type": "http",
      "url": "https://autumn-web.app/mcp"
    } } }

How Autumn builds MCP servers