Releases

Tokio Team Launches Toasty, an Async ORM Built for Rust Productivity

Carl Lerche spent two-plus years building Toasty; the Tokio team's async ORM hit crates.io with SQL and DynamoDB support baked in.

Nina Kowalski3 min read
Published
Listen to this article0:00 min
Share this article:
Tokio Team Launches Toasty, an Async ORM Built for Rust Productivity
Source: media.licdn.com
This article contains affiliate links, marked with a blue dot. We may earn a small commission at no extra cost to you.

Carl Lerche made the first commit to Toasty more than two years before it reached crates.io. On April 3, 2026, he finally shipped it.

That gap is the story. The AWS Principal Engineer who created Tokio, the async runtime carrying over 31,500 GitHub stars and the de facto standard for server-side Rust, spent those two years building an ORM designed to do for Rust web backends what Rails once did for Ruby: make them feel obvious.

Toasty is an async-first, opinionated Object-Relational Mapping library that prioritizes ergonomics over flexibility. It uses derive macros, supports relationships through has_many and belongs_to constructs, and ships with support for SQLite, PostgreSQL, and MySQL on the SQL side, plus DynamoDB on the NoSQL side. Cassandra support, which Lerche previewed in his October 2024 announcement, is still pending at launch.

The library's design philosophy reflects a deliberate choice Lerche has been vocal about: Toasty does not abstract away database differences. As the launch post states, "Toasty does not hide the database capabilities. Instead, Toasty exposes features based on the target database" — meaning a DynamoDB-backed app and a PostgreSQL-backed app will intentionally surface different access patterns reflecting each system's real constraints.

Lerche first showed Toasty publicly on October 23, 2024, on the Tokio blog, labeling it a preview "not ready for real-world usage yet" and deliberately withholding a crates.io release. He made the case at his QCon San Francisco 2024 keynote, titled "Rust: a Productive Language for Writing Database Applications," that Rust needed better tooling at this layer of the stack. InfoQ, covering the talk, noted that Lerche emphasized ease of use over pure performance.

AI-generated illustration
AI-generated illustration

The existing ORM landscape reflects the historical tension Lerche is trying to resolve. Diesel, which pioneered compile-time SQL checking and shipped its 1.0 in 2018, remains a production staple but is synchronous by design. SeaORM, the closest async competitor to Toasty, reached 1.0 in Summer 2024 and version 2.0 in January 2026. SQLx, the most widely used async SQL toolkit, offers direct query control at the cost of boilerplate. Community commentary following the 2024 preview suggested Toasty threads that needle by combining Diesel's compile-time column safety with SeaORM's builder ergonomics.

One Lobste.rs commenter put the release's institutional weight plainly: "The Tokio team basically runs the Rust ecosystem, so a first-party ORM from them is pretty exciting." A JetBrains RustRover blog post from February 2026 had already documented Tokio as "the de facto standard largely due to ecosystem momentum," with early adopters like Hyper pulling the rest of the server-side community along. An ORM carrying that provenance enters with credibility a standalone crate would spend years earning.

The launch post also addressed AI directly: "Let's be real, the cat is out of the bag — many developers are going to let AI take the wheel. Rust's strong type system and guardrails are going to be an asset there." Lerche framed Rust's strictness as a feature in an AI-assisted development workflow rather than a barrier, and Toasty's ergonomics as a way to lower the remaining friction.

The Toasty repository had approximately 1,978 stars and 71 forks at launch. TokioConf 2026, scheduled for April 20-22 in Portland, Oregon, will bring together Alice Ryhl, Nicholas Matsakis, Glauber Costa, and Steve Klabnik, giving the community a near-term venue to push the project's next phase forward, including the still-outstanding Cassandra backend.

Know something we missed? Have a correction or additional information?

Submit a Tip

Discussion

More Rust Programming News