I built Altus 4 because I was frustrated with spinning up Elasticsearch/Solr just to get decent search.
Many apps already use MySQL, but its built-in FULLTEXT search is often too basic.
Altus 4 bridges that gap:
- Adds AI-powered semantic search on top of MySQL FULLTEXT
- Handles natural language queries ("show me users from last month in London")
- Optimizes queries and provides performance insights
- Works across multiple databases without extra infrastructure
- Includes analytics, monitoring, and API key auth out of the box
It’s open source (Apache 2.0) and runs in Node.js + TypeScript, with MySQL + Redis underneath.
You can be up and running in minutes without migrating your stack.
I built Altus 4 because I was frustrated with spinning up Elasticsearch/Solr just to get decent search. Many apps already use MySQL, but its built-in FULLTEXT search is often too basic.
Altus 4 bridges that gap: - Adds AI-powered semantic search on top of MySQL FULLTEXT - Handles natural language queries ("show me users from last month in London") - Optimizes queries and provides performance insights - Works across multiple databases without extra infrastructure - Includes analytics, monitoring, and API key auth out of the box
It’s open source (Apache 2.0) and runs in Node.js + TypeScript, with MySQL + Redis underneath. You can be up and running in minutes without migrating your stack.
- Project website: https://altus4.thavarshan.com/ - GitHub: https://github.com/altus4/core - Docs: https://altus4.thavarshan.com/docs/ - Why I built it (Dev.to): https://dev.to/thavarshan/building-altus-4-why-i-created-an-...
I’d love feedback — especially from people running MySQL in production. Does this scratch an itch for you? What would make it more useful?