Autumn 🍂

Spring Boot-style web framework for Rust, built on Axum.

Autumn assembles proven Rust crates into a convention-over-configuration web stack with proc-macro ergonomics, framework defaults, and customization options when you need them. If Spring Boot, Rails, or Laravel feels familiar, Autumn aims for that same "ship the app, not the plumbing" shape in Rust.

Features

• Route and app macros - #[get], #[post], #[put], #[delete], routes![], #[autumn_web::main]
• Pre-rendering pages to static HTML - #[static_get] + static_routes![] with autumn build pre-rendering to dist/
• Application builder - .routes(), .tasks(), .static_routes(), .scoped(), .merge(), and .nest()
• Configuration and profiles - defaults, autumn.toml, autumn-{profile}.toml, and AUTUMN_* overrides
• Database ergonomics - async Postgres primary/replica pools, Db extractor for the primary/write role, #[model], #[repository], hooks, and embedded migrations
• HTML stack - Maud templating, bundled htmx, Tailwind build pipeline, and static asset serving
• Operations - /health, /actuator/*, structured logging, metrics, and graceful shutdown
• Background work - #[scheduled] tasks, #[job] handlers, one-off #[task] scripts via autumn task, and runtime task visibility at /actuator/tasks
• Companion workflows - Autumn Harvest is the separate durable workflow engine for multi-step orchestration when #[scheduled] or #[job] is not enough
• Transactional email - optional mail feature with Maud templates, log/file/SMTP transports, and a Mailer extractor
• Security primitives - session cookies, auth extractor, security headers, CSRF, and #[secured]
• File storage (optional) - pluggable BlobStore trait with built-in Local and S3-compatible backends, HMAC-signed URLs, and MultipartField::save_to_blob_store (see storage guide)
• CLI workflow - autumn new, autumn setup, autumn dev, autumn build, autumn migrate, and autumn task

Quickstart

# Install the published CLI

cargo install autumn-cli --version 0.4.0


# Local development only, from an Autumn checkout:

# cargo install --path autumn-cli


# Create a new project

autumn new my-app

cd my-app


# Optional: download Tailwind CSS for styled builds

autumn setup


# Optional: scaffold a CRUD resource (see docs/guide/generators.md)

# autumn generate scaffold Post title:String body:Text published:bool


# Development server with file watching

autumn dev


# Or run without watch mode

# cargo run

Visit http://localhost:3000. Autumn also auto-mounts /health, /actuator/health, /actuator/info, and /static/js/htmx.min.js.

Watching custom directories

autumn dev always watches src/, static/, templates/, and migrations/ plus the project's top-level config files (autumn.toml, Cargo.toml, Cargo.lock, build.rs, tailwind.config.js). To watch additional folders (for example, custom view or locale trees), add a [dev] section to autumn.toml:

[dev]

watch_dirs = ["views", "locales"]

Listed directories are watched recursively in addition to the defaults. Multi-segment paths like content/locales are supported. Changes inside them trigger a server restart and a full browser reload. Paths under target/ and dotted directories are still ignored.

Entries must be project-relative; absolute paths, .. traversal, target, and dotted directories (e.g. .git) are rejected with a warning. Missing directories are skipped at startup.

If you add #[static_get] routes, autumn build pre-renders them into dist/.

Local-Safe vs Production-Safe

Autumn still distinguishes between "works on your laptop" and "safe to run in a multi-replica deployment":

• Local-safe defaults: in-memory sessions, pretty logs in dev, scheduler.backend = "in_process" for #[scheduled], and single-binary startup.
• Production-safe options: /live, /ready, /startup probes, OTLP telemetry config, Redis-backed sessions, Redis-backed channels/jobs, Postgres-coordinated scheduled tasks, container scaffolding from autumn new, and explicit migration jobs before web replicas roll.

If you are deploying beyond a single process, read the Cloud-Native Guide before treating the defaults as done.

Database Topologies

Autumn supports three explicit database shapes:

• Single primary: set database.url or database.primary_url. Writes, transactions, advisory locks, and autumn migrate use that primary role.
• Primary plus read replica: set database.primary_url and database.replica_url, with optional primary_pool_size, replica_pool_size, and replica_fallback = "fail_readiness" or "primary".
• One-shot migrator path: run autumn migrate once against the primary before rolling web replicas. Production web replicas should keep auto_migrate_in_production = false.

database.url and DATABASE_URL remain valid for existing single-URL apps. For new production config, prefer AUTUMN_DATABASE__PRIMARY_URL so the write role is named plainly. autumn doctor --strict reports missing primaries, unsafe production startup migrations, role connectivity failures, and stale replica migrations without printing credentials.

Autumn Harvest

Autumn Harvest is the companion workflow engine for durable, multi-step work: workflow history, activity retries, timers, singleton orchestration, and long-running business processes. It is intentionally a separate release train from autumn-web: Harvest can depend on Autumn Web's AppState and builder surface, but Autumn Web's examples and tests should not need Harvest in order to ship a web release. That keeps the dependency graph pointed in one direction instead of forming a circular release dependency.

Use built-in #[scheduled] tasks and #[job] handlers for lightweight app-local background work. Reach for Harvest when the work needs workflow durability or a dedicated runner. See the Harvest architecture notes for the model and roadmap.

Example

This is the small-app shape Autumn is built around:

use autumn_web::prelude::*;

#[get("/")]
async fn index() -> &'static str {
    "Welcome to Autumn!"
}

#[get("/hello/{name}")]
async fn hello_name(name: autumn_web::extract::Path<String>) -> String {
    format!("Hello, {}!", *name)
}

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

Built On

• Axum - async HTTP routing and middleware
• Diesel + diesel-async - database access
• Maud - compiled HTML templates
• htmx - HTML-first interactivity
• Tailwind CSS - utility-first styling
• Tokio - async runtime
• Tracing - structured logging

Examples

See EXAMPLES.md for the full catalog with personas, journeys, prerequisites, run commands, and success proofs.

Documentation

• Getting Started Guide
• Signed Webhook Intake
• Docs Smoke Procedure - release gate for first-run docs
• Release Checklist
• Code Generators — autumn generate model | migration | scaffold
• One-Off Tasks - #[task], one_off_tasks![], and autumn task
• Multi-Replica Scheduled Tasks - #[scheduled] with Postgres advisory-lock coordination
• Operating Background Jobs - admin dashboard and recovery actions for #[job]
• Mail Guide
• Cloud-Native Guide
• Todo Tutorial
• Autumn Harvest Architecture Notes
• API Reference
• Pre-rendering Design Notes
• Stability Policy — SemVer, MSRV, and migration commitments

Stability

Autumn commits to Semantic Versioning for its public API starting at 1.0.0. See STABILITY.md for the full definition of the stable surface, the MSRV policy, and the migration-guide process for future major releases.

Until 1.0.0, Autumn is in its 0.x series — see the pre-1.0 notes for what that means in practice.

Requirements

• Rust 1.88.0+ (edition 2024)
• PostgreSQL for database-backed apps

Autumn can still run without a database if you omit the [database] section.

License

MIT OR Apache-2.0