tokio-rs/toasty

An async ORM for Rust

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on October 22nd, 2024
Open Issues & Pull Requests: 106 (+0)
GitHub issues: Enabled
Number of forks: 138
Total Stargazers: 3,121 (+1)
Total Subscribers: 23 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.4 days
Mean response time: 26.7 days
90th percentile: 98.2 days
Tracked items: 187

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 57% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "A-macros" is answered fastest, typically in about 2 days, while "A-schema" waits about 4 weeks. 48% of tracked open issues have had no activity in three months. 64% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 83
New in 7 days: 4
Closed in 7 days: 11
Avg open age: 123 days
Stale 30+ days: 69
Stale 90+ days: 34

Recent activity

Opened in 7 days: 4
Closed in 7 days: 11
Comments in 7 days: 1
Events in 7 days: 3

Top labels

  • C-feature (83)
  • C-bug (68)
  • A-engine (54)
  • A-driver (36)
  • A-macros (35)
  • A-schema (26)
  • A-migration (23)
  • C-enhancement (14)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Toasty is an async ORM for Rust that supports both SQL and NoSQL databases including SQLite, Turso, PostgreSQL, MySQL, and DynamoDB.

The tool addresses the challenge of building applications that work across different database systems by refusing to hide database-specific capabilities. Rather than abstracting away differences, Toasty exposes features based on the target database, allowing developers to leverage each database's strengths while avoiding inefficient queries. You define your data model using Rust structs with the `#[derive(toasty::Model)]` derive macro, and the ORM generates appropriate query methods based on what the target database can efficiently execute. For SQL databases, arbitrary query constraints may be allowed, while for NoSQL systems like DynamoDB, only constraints matching the database's indexed access patterns are generated.

Toasty suits projects that need to work with multiple database backends or want to avoid the performance pitfalls of over-abstracted ORMs. It is particularly valuable when you want to decouple your application data model from the underlying database schema while still maintaining control over how that mapping works. The tool allows customization through annotations to control how the application model maps to the database schema. Choose Toasty if you prefer an ORM that respects database differences rather than hiding them, and if you want compile-time generation of safe query methods tailored to your specific database.

The project maintains a public roadmap documenting development priorities, which are shaped by user feedback and contributions. The contribution process distinguishes between small fixes that can proceed directly to pull requests and larger changes that follow a propose-roadmap-design-implement flow. The team actively solicits issue reports and pull requests when users encounter missing features or rough edges.