OSS TanbouSign in with GitHub

bootstrap Rust backends with Rails-style conventions, generators, ORM, jobs, and storage

OSS scale score 245.8OSS health 100
About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
9,397
Primary language
Rust
License
Apache-2.0
Repository last updated
Sep 24, 2026
On this page

Overview

Loco is a Rust application framework inspired by Ruby on Rails. It combines Axum controllers, SeaORM models, background jobs, scheduling, mailers, storage, and caching under convention-over-configuration defaults.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Combine controllers, ORM, jobs, mailers, and storage in one application structure

Loco standardizes Axum-based controllers, SeaORM models, Redis or in-process jobs, scheduling, mail delivery, storage, and caching within one framework.

Sources: [2]

Generate SaaS or API application scaffolds from conventions

loco new generates an application template and lets developers choose database and worker options, reducing boilerplate around common backend structure.

Sources: [2]

Best fit

Fits small teams rapidly building product backends with CRUD, auth, and background work

It is useful when a project prefers a cohesive application framework over selecting and wiring each web, database, worker, and storage component independently.

Sources: [2]

Before adoption

Check Rust 1.94+ and generated scaffold behavior when upgrading

Loco 1.2.0 raises its MSRV to Rust 1.94 for SeaORM 2.0 and sqlx 0.9. The release also changes queue-provider errors, adds multi-tenancy, improves Redis worker recovery, and fixes generated routes and SPA scaffolds, so existing apps should compare generated templates as well as framework APIs.

Sources: [3][4]

Official sources

  1. [1]loco-rs/loco — GitHub repository(2026-10-06)
  2. [2]Loco 1.2.0 — README(2026-10-06)
  3. [3]Loco 1.2.0 — Cargo.toml(2026-10-06)
  4. [4]Loco 1.2.0 release(2026-10-06)
Supplemental curator note

Loco fits teams that want an application framework with generators, conventions, jobs, mailers, and storage rather than assembling Axum and SeaORM manually. Generated scaffold changes deserve explicit review during upgrades.

Try it in 3 steps

  1. 1

    Install Loco CLI 1.2.0

    Install the reviewed Loco CLI version. Loco 1.2.0 requires Rust 1.94 or newer.

    cargo install loco --version 1.2.0
  2. 2

    Generate an application

    Follow the README flow, for example naming the app myapp and selecting the SaaS template, SQLite, and the async worker option.

    loco new
  3. 3

    Start the generated server

    Start the generated application and verify the Loco controller, database, and application lifecycle.

    cd myapp && cargo loco start
Check the official README

Growth

Growth trends · Last 30 days

9,397 Stars

Trend data is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • api
  • axum
  • rust
  • rust-lang
Stars
9,397
Forks
438
Watchers
55
Open issues
28
Contributors
152
Owner type
Organization
Primary language
Rust
License
Apache-2.0
Repository last updated
Sep 24, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?