Learn how Manticore Search and Typesense differ in their key features, development activity, technology stack and community adoption, so you can decide which of these search engines is best for you.
Last 30 days
Last commit
12 hours agoRepository age
9 yearsVersion
29.9.0License
GPL-3.0Self-hosted
YesRepository
manticoresearch
Last 30 days
Last commit
2 days agoRepository age
10 yearsVersion
v30.2License
GPL-3.0Self-hosted
YesRepository
typesense/typesense
Typesense appears to have several advantages over Manticore Search, particularly in popularity and growth. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Typesense leads in popularity with 27,091 stars vs 12,075 stars for Manticore Search. The 124% higher star count indicates stronger community adoption. In terms of developer contributions, Typesense has 1,027 forks, indicating strong developer engagement.
Typesense is growing faster, adding 457 stars in the last 30 days (+1.7%) against adding 33 stars for Manticore Search (+0.3%). Typesense is both larger and pulling further ahead.
Both projects show recent activity, with Manticore Search last updated 12 hours ago and Typesense 2 days ago.
Both tools share common technology foundations, being built with Bash, C, Objective-C, C++. However, they differ in their additional technology choices: Manticore Search uses Python, PHP, Java, Ruby, C#, Perl while Typesense leverages JavaScript, Typescript.
Both projects started around the same time, with Manticore Search beginning 9 years ago and Typesense 10 years ago.
Both projects use the GPL-3.0 license, providing identical terms for usage and distribution.
Both tools serve similar use cases in Search Engines.
Both Manticore Search and Typesense offer self-hosting capabilities, giving you full control over your data and infrastructure.