Meilisearch vs WeWeb
Side-by-side trajectory, velocity, and editorial themes.
Meilisearch hardens auth and speeds synonyms as its new settings indexer nears completion
Meilisearch is on a fast weekly point-release cadence centered on engine performance and security. Its new settings indexer reached feature-complete in v1.47, synonym storage was reworked for up to 13x faster search on large synonym sets, and two authentication CVEs were patched across the 1.47 and 1.48 branches. Experimental work on a render-template route and multimodal fragments points at deeper embedder tooling underneath the search core.
The near-term arc is consolidation: finishing the settings-indexer migration, tightening authentication, and stabilizing the S3 snapshot and remote-federated-search paths. The experimental render-template and fragment routes suggest Meilisearch is building out its vector and multimodal search story so document templates and embedders can be tested and iterated before indexing.
Expect v1.50 to graduate some of the experimental render-template and embedder tooling toward stable, while security and settings-indexer hardening continue in the point releases.
WeWeb is going AI-native, letting external tools build in your project
WeWeb is pushing its visual web builder toward AI-native development. It shipped MCP support so external AI tools can understand and build directly in a WeWeb project, then followed with in-app WeWeb AI gaining planning and task tracking plus MCP quality-of-life fixes. Underneath, the core keeps getting refined — a redesigned Supabase Select, formula columns in table views, and steady editor, navigation, and publishing polish.
The arc is toward a builder where AI is a first-class way to construct apps, whether through the in-app assistant or an external tool driving the project over MCP. Recent releases pair that agentic surface with data-layer depth (Supabase, formula columns) and deployment ergonomics, suggesting WeWeb wants AI-assisted building to sit on top of a solid, data-connected foundation rather than replace it. The messaging around 'AI, visual, or both' signals a deliberately hybrid workflow.
Expect WeWeb AI and MCP to keep maturing together — richer planning, more reliable agent edits — alongside continued Supabase and data-source depth, given how these two threads dominate the recent cadence.
See more alternatives to Meilisearch →
See more alternatives to WeWeb →