Learn how Dray and Paseo differ in their key features, development activity, technology stack and community adoption, so you can decide which of these ai coding agent orchestrators is best for you.
Last 30 days
Last commit
7 hours agoRepository age
4 monthsVersion
v0.30.2License
Apache-2.0Repository
monorepo-labs/dray
Last 30 days
Last commit
7 hours agoRepository age
1 yearVersion
v0.15.4License
Apache-2.0Self-hosted
YesRepository
getpaseo/paseo
Paseo appears to have several advantages over Dray, particularly in popularity, growth and features. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Paseo significantly outpaces Dray in community adoption with 23,944 stars compared to 130 stars on GitHub. This 184.2x difference suggests Paseo has a much larger and more active community. In terms of developer contributions, Paseo has 2,938 forks, indicating strong developer engagement.
Paseo is growing faster, adding 3,063 stars in the last 30 days (+15%) against adding 16 stars for Dray (+14%). Paseo is both larger and pulling further ahead.
Both projects show recent activity, with Dray last updated 7 hours ago and Paseo 7 hours ago.
Both tools share common technology foundations, being built with JavaScript, CSS, Bash, Typescript, JSX. However, they differ in their additional technology choices: Dray uses Next.js, Rust, Tauri while Paseo leverages Swift, Ruby, Kotlin, Tanstack Start.
Both projects started around the same time, with Dray beginning 4 months ago and Paseo 1 year ago.
Both projects use the Apache-2.0 license, providing identical terms for usage and distribution.
Both tools serve similar use cases in AI Coding Agent Orchestrators.
Paseo provides self-hosting options for complete data control and customization, while Dray may be primarily cloud-based or require different deployment approaches.