Learn how Neon Postgres and Turso differ in their key features, development activity, technology stack and community adoption, so you can decide which of these relational databases (sql) is best for you.
Last 30 days
Last commit
Repository age
License
Repository

Last 30 days
Last commit
Repository age
Version
License
Repository

Both Neon Postgres and Turso have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Both tools have similar popularity levels, with Neon Postgres having 22,901 stars and Turso having 17,147 stars on GitHub. In terms of developer contributions, Neon Postgres has 1,060 forks, indicating strong developer engagement.
Neon Postgres and Turso are moving at much the same rate, adding 278 stars and adding 172 stars respectively over the last 30 days (+1.2% vs +1%). Neither is pulling away from the other on momentum alone.
Turso shows more recent development activity with its last commit 8 days ago, while Neon Postgres was last updated 3 months ago. This suggests Turso is being more actively maintained.
Both tools share common technology foundations, being built with JavaScript, Bash, Python, C, Rust, Objective-C, Java, C#. However, they differ in their additional technology choices: Neon Postgres uses Swift while Turso leverages CSS, Typescript, C++, Lua.
Neon Postgres has been in development longer, starting 5 years ago, compared to Turso which began 4 years ago. This 1.5-year head start suggests Neon Postgres may have more mature features and established processes.
Turso uses the MIT license, which is more permissive than Neon Postgres's Apache-2.0 license, potentially offering greater flexibility for commercial use and integration.
Both tools serve similar use cases in Relational Databases (SQL).