teo
Teo is an open-source, high-performance ORM library for Rust that supports multiple databases (MySQL, PostgreSQL, SQLite, MongoDB) with async-first design. It emphasizes ergonomic query APIs and incremental migrations, though it is currently in work-in-progress status.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | teodevgroup/teo |
| Owner | teodevgroup |
| Primary language | Rust |
| License | MIT — OSI-approved |
| Stars | 1.4k |
| Forks | 45 |
| Open issues | 0 |
| Latest release | Unknown |
| Last updated | 2026-02-12 |
| Source | https://github.com/teodevgroup/teo |
What teo is
Teo is a fully asynchronous Rust ORM providing database abstraction across relational (MySQL, PostgreSQL, SQLite) and NoSQL (MongoDB) backends. It offers type-safe query construction and incremental schema migration tooling, with active development indicated by recent commits despite no tagged releases.
Get the teo source
Clone the repository and explore it locally.
git clone https://github.com/teodevgroup/teo.gitcd teo# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Verify feature flags and database driver support match your deployment target (postgres, mysql, sqlite, mongodb) before committing to a version.
- Plan for potential breaking changes; WIP status and absence of versioning discipline mean minor updates may not follow semantic versioning strictly.
- Evaluate async runtime compatibility—confirm Teo's runtime (likely Tokio) aligns with your application architecture.
- Test incremental migration strategy against your branching and deployment workflow; schema evolution tooling maturity is Unknown.
- Establish fallback plans or vendor relationships for critical issues, as community support and response SLAs are not documented.
When to avoid it — and what to weigh
- Production Stability Critical Without Support — Project is explicitly marked WIP. No tagged releases, limited adoption signals (1407 stars, 0 open issues may indicate small user base or early-stage stability), and absence of commercial support channels raise risk for mission-critical deployments.
- Existing ORM Ecosystem Lock-In — Organizations already committed to Diesel, SQLx, or Prisma may face friction adopting a younger ORM. Migration tooling and community plugins are Unknown.
- Complex Legacy Schema Support — Unknown how well Teo handles reverse-engineering or mapping complex, non-standard schemas. WIP status suggests tooling may not yet cover edge cases common in brownfield projects.
- Regulated Compliance Environments — No clear audit trail, security policy, or third-party security assessment publicly documented. Regulatory requirements (HIPAA, SOC2, etc.) should trigger explicit vendor/security review.
License & commercial use
Licensed under MIT (permissive OSI-approved license). Allows use, modification, and distribution with minimal restrictions provided the license and copyright notice are included.
MIT license permits commercial use without explicit permission. However, MIT provides no indemnification, warranty, or support. For production use, especially in regulated industries or high-availability contexts, evaluate whether the lack of a commercial backing or SLA is acceptable risk.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | Medium |
No formal security policy, responsible disclosure process, or third-party audit mentioned. Teo is a data access layer—review it for SQL injection prevention, prepared statement support, and secrets management. WIP status means security-relevant bugs may be discovered post-deployment. For sensitive data or compliance-critical systems, conduct code review and threat modeling before adoption.
Alternatives to consider
Diesel
Mature, battle-tested Rust ORM with strong type safety and compile-time verification. Supports PostgreSQL, MySQL, SQLite. Stable API with longer release history; better for risk-averse production deployments.
SQLx
Async-first, compile-time checked SQL with lower abstraction overhead. No runtime schema introspection; simpler mental model. Excellent for projects prioritizing explicit control and avoiding ORM magic.
Prisma (prisma-client-rust)
Higher-level ORM with schema-driven code generation and multi-database support (similar scope to Teo). Backed by commercial company; more stable versioning and support channels. Learning curve steeper but ecosystem more mature.
Build on teo with DEV.co software developers
We can help architect async database layers, assess multi-backend integration, and navigate WIP tooling maturity. Let's discuss your requirements and build a migration or deployment strategy.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
teo FAQ
Is Teo production-ready?
Can I use Teo with MongoDB and PostgreSQL in the same app?
What async runtime does Teo require?
How do I report security issues?
Work with a software development agency
Need help beyond evaluating teo? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source databases integrations — and maintain them long-term.
Evaluating Teo for Your Rust Backend?
We can help architect async database layers, assess multi-backend integration, and navigate WIP tooling maturity. Let's discuss your requirements and build a migration or deployment strategy.