Rustango docs
← Getting started

Why Rustango: an honest comparison

Rustango is a batteries-included web framework for Rust: declare a model once and get an ORM, migrations, an admin, a REST API and multi-tenancy out of it. This page sets out what it is good at, how it compares with the frameworks people usually reach for, the benchmark numbers, and where you should still pick something else.

The short version

  • Choose Rustango when you want the productivity of a batteries-included framework with the speed, memory use and compile-time checking of Rust, and one binary to deploy.
  • Choose something else when your team does not write Rust, when you need a huge package ecosystem today, or when you want a framework with a decade of production history.

What is in the box

AreaRustango
ORMOne model, correct SQL for PostgreSQL, MySQL 8+ and SQLite; relations, aggregates, soft delete
MigrationsGenerated by comparing your models with the last snapshot, then applied
AdminAn auto-generated admin with search, filters, audit log and permissions
APIsViewSets and serializers for REST, OpenAPI generated from them
AuthSessions, JWT, OAuth2 / OIDC, single sign-on, API keys, HMAC, TOTP, passkeys
Multi-tenancySchema per tenant (PostgreSQL) or database per tenant (all three databases)
Background workJobs, scheduled tasks, signals, email, file storage
SecurityCSRF, rate limits, login throttling, security headers, CORS, allowed hosts
AI agentsA built-in MCP server
ToolingA project scaffolder, generators and one manage command line

Everything beyond the ORM is a cargo feature, so a JSON-only API compiles the admin and templates out entirely.

How it compares

RustangoDjangoRailsLaravelLocoaxum + sqlx
LanguageRustPythonRubyPHPRustRust
ORMBuilt inBuilt inBuilt inBuilt inSeaORMQueries by hand
Migrations from modelsYes, diffedYes, diffedWritten with generatorsWritten by handWritten with generatorsBy hand
AdminBuilt inBuilt inGemsPackages (Nova, Filament)NoNo
REST API layerBuilt in, with OpenAPIPackage (DRF)Built in (API mode)Built inBuilt inBy hand
Multi-tenancyBuilt inPackagesGemsPackagesNoBy hand
Background jobsBuilt inTasks API; worker via a packageBuilt inBuilt inBuilt inBy hand
Errors in models and queriesCaught at compile timeAt run timeAt run timeAt run timeCaught at compile timeCaught at compile time
Deploy artefactOne binaryApp + Python runtimeApp + Ruby runtimeApp + PHP runtimeOne binaryOne binary
EcosystemSmall and newHugeHugeHugeGrowingLarge (Rust crates)

The honest reading: on features, Rustango is in the same class as Django and Rails, not ahead of them. It wins on speed, memory, compile-time safety and deployment, and against the other Rust options it wins on everything that comes in the box.

Benchmarks

Every app served the same blog: 1 000 posts, 10 000 comments, the same HTML checked byte for byte, 4 CPUs, 16 database connections, 50 concurrent connections. The full method, the limits and the profiles are in the benchmark write-up. Numbers from different rounds were measured separately, so each table stays within one round.

Round 2: compiled apps (requests per second, higher is better):

AppIndexDetailTagIndex, cachedMemory under load
Rustango · actix17 40127 2927 056231 9756.3 MiB
Rustango · axum14 68625 7887 090174 5016.9 MiB
axum + sqlx14 14022 8426 467198 6697.6 MiB
actix + sqlx14 40821 6306 628226 8877.2 MiB
Rocket13 31624 5616 836138 2248.7 MiB
Loco10 29015 6355 604153 24312.0 MiB
Go (net/http + pgx)8 74122 6076 38691 83922.8 MiB

Rustango, with its ORM, is the fastest of the eight on uncached pages, ahead of hand-written queries on raw sqlx.

Round 1: interpreted runtimes, with Rustango from the same run (the 0.60.6 release, before the round 2 fixes):

AppUncached index, req/sCached index, req/sMemory under load
Rustango · actix6 341200 167~7 MiB
Laravel · Octane1 0985 884241 MiB
Python · gunicorn69711 012224 MiB
WordPress59921 285142 MiB
Laravel · php-fpm5183 32689 MiB

The honest caveats

  • Go is faster at pure computation, by 8–17% in the compute test, and plain axum with sqlx serves the cached index faster than Rustango on axum (198 669 against 174 501 req/s).
  • It is young. Version 0.x, with a large surface still settling. Recent releases have added rather than removed, but read the changelog when you upgrade.
  • The ecosystem is small. Django, Rails and Laravel have a package for almost anything; with Rustango you will more often write it yourself or reach for a general Rust crate.
  • Rust has a learning curve, and compile times are real: minutes for a first build, seconds for a change.
  • Schema-per-tenant needs PostgreSQL. On MySQL and SQLite, tenants get a database each.
  • The benchmarks have limits. One laptop, a Docker VM, a read-heavy server-rendered workload. No writes, auth flows or heavy business logic. Your numbers will differ.

Who should use it

  • Teams that like Django's or Rails' way of working but want Rust's speed, safety and small footprint.
  • Rust teams tired of assembling the same auth, admin, migrations and API layers on every project.
  • Multi-tenant SaaS products that want tenancy in the framework rather than bolted on.

Try it

cargo install cargo-rustango
cargo rustango new myapp
cd myapp && cargo run

The getting-started guide builds a blog with an admin, a JSON API and sign-in step by step. For content sites, Rustango-CMS is built on top of it.