tokio-rs

    tokio-rs/toasty

    An async ORM for Rust

    database
    Rust
    MIT
    3.3K stars
    151 forks
    3.3K GitHub watchers
    Updated Oct 31, 2026
    View on GitHub

    Build with Backblaze B2

    SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.

    Explore Backblaze Labs

    Loading star history...

    Where it stands

    Rank, growth pace and release cadence relative to everything GStars tracks.

    2 releases in the last 90 days, the latest 36 days ago, with 56 contributors on GitHub.

    Use Cases & Benefits

    • Provides an async ORM for Rust supporting SQL and NoSQL databases with native database feature exposure.
    • Enables efficient, idiomatic Rust data modeling while leveraging each database's unique capabilities without abstraction loss.
    • Use for building type-safe, asynchronous Rust applications with complex relational data models across multiple database types.
    • Use for integrating Rust services with DynamoDB or SQL databases while optimizing queries for each backend's strengths.
    • Use for developing Rust projects requiring flexible schema mapping between application models and diverse database schemas.

    Should you depend on it?

    License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.

    License

    MIT

    Permissive: commercial use, modification and redistribution are allowed with attribution.

    Community files

    • README: present
    • Contributing guide: present

    Watch-outs

    No watch-outs from GStars' checks.

    General guidance from repository metadata, not legal advice. How we score

    From the README

    The cozy, easy ORM for Rust Guide • API Docs • Crates.io • Discord

    Toasty supports SQL databases (SQLite/Turso, PostgreSQL, MySQL) and DynamoDB. It does not hide database capabilities — it exposes features based on the target database.

    You will define your data model using Rust structs annotated with the #[derive(toasty::Model)] derive macro. Runnable examples live in the examples/ directory; the snippets below illustrate the basics.

    Toasty supports both SQL and NoSQL databases. Current drivers are SQLite, Turso, PostgreSQL, MySQL, and DynamoDB. However, it does not aim to abstract the database. Instead, Toasty leans into the target database's capabilities and aims to help the user avoid issuing inefficient queries for that database.

    When targeting both SQL and NoSQL databases, Toasty generates query methods (e.g. get_by_id only for access patterns that are indexed). When targeting a SQL database, Toasty might allow arbitrary additional query constraints. When targeting a NoSQL database, Toasty will only allow constraints that the specific target database can execute. For example, with DynamoDB, query methods might be generated based on the table's primary key, and additional constraints may be set for the sort key.

    Excerpt from the tokio-rs/toasty README on GitHub (MIT license). © its authors.Read the full README on GitHub

    Daily snapshots

    Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots

    Sep 27: +12

    +124 stars over 36 days across 4 snapshot days; best day +12 on Sep 27.

    Forks

    151+9

    Open issues

    108+1

    Compared with peers in Database

    Fastest-growing repositories GStars tracks in this cohort for the week of Nov 1, by 7-day star growth

    tokio-rs/toasty compared with Database repositories by stars, 7-day star growth, health score and last release
    RepositoryStars+7dHealthLast release
    thedotmack/claude-mem113.6K+8.8K35today
    t8y2/dbx29.1K+1.0K40today
    gitroomhq/postiz-app41.0K+8656412 days ago
    supabase/supabase114.6K+2686090 days ago
    juicedata/juicefs14.7K+1056414 days ago
    tokio-rs/toasty3.3K—5836 days ago
    Category median41.0K+86560—

    Also by tokio-rs

    Other repositories from this maintainer that GStars tracks

    Discover Repositories

    Search across tracked repositories by name or description