Botsify
Botsify publishes buying guides, not release notes — the product stays out of view
A side-by-side editorial comparison of Perplexity and Deep Lake — release velocity, themes, recent moves, and the top alternatives to consider.
Perplexity is selling access to other people's models, not just its own answers.
The recent changelog is almost entirely API-side. A Gateway API fronts open-weight models behind one endpoint that speaks both OpenAI Chat Completions and Anthropic Messages, a remote MCP server exposes Perplexity to outside agents, and the Agent API keeps absorbing new models. Consumer-facing notes — preset tuning, inline citations for research presets — read as maintenance beside that.
Deep Lake is rebuilding itself as a Postgres extension.
The visible release history is thin — three entries spanning a version 3 patch and two version 4 releases. The 4.x work splits between the core dataset format and pg_deeplake, a Postgres extension that has been gaining SQL type support, automatic table reload and library preloading. The 4.4.1 release added a storage directory listing API, mesh type support, PLY visualisation, a simple visualiser, and a 30% improvement in LRU cache insertion time.
The recent changelog is almost entirely API-side. A Gateway API fronts open-weight models behind one endpoint that speaks both OpenAI Chat Completions and Anthropic Messages, a remote MCP server exposes Perplexity to outside agents, and the Agent API keeps absorbing new models. Consumer-facing notes — preset tuning, inline citations for research presets — read as maintenance beside that.
The product is splitting in two: an answer engine for end users and an inference-and-routing layer for developers. Price moves in the same window, a GPT-5.6 cut and a faster low-cost mode, put Perplexity in a cost-per-token argument rather than an answer-quality one. Building the gateway to mimic the two dominant API dialects makes the switching cost it removes its own.
Expect more hosted open-weight models behind the gateway and firmer pricing tiers, with the remote MCP server moving from a listed feature to a documented, permissioned surface.
The visible release history is thin — three entries spanning a version 3 patch and two version 4 releases. The 4.x work splits between the core dataset format and pg_deeplake, a Postgres extension that has been gaining SQL type support, automatic table reload and library preloading. The 4.4.1 release added a storage directory listing API, mesh type support, PLY visualisation, a simple visualiser, and a 30% improvement in LRU cache insertion time.
Two things stand out. The query engine was separated from the execution module and group-by execution was pulled out on its own, which is architecture work done ahead of features rather than after them. And the pg_deeplake investment points at meeting users inside the database they already query rather than asking them to adopt a separate dataset API. Version-locked read-only views fit the same picture — reproducible reads for teams treating datasets as versioned artefacts.
The query core separation and group-by refactor were both described as groundwork, so query execution features are the likely next visible step in pg_deeplake.
Other ai-assistants products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Perplexity or Deep Lake.
Botsify publishes buying guides, not release notes — the product stays out of view
OpenVINO is chasing every new model release while quietly moving under llama.cpp.
KServe now releases almost entirely for its LLM inference service.
NeMo split itself apart: the flagship repo is now a speech toolkit and nothing else.
Copilot's build-out has shifted from model drops to enterprise controls and spend accounting.
The desktop app is where the work is going, and it just learned to speak everyone's language.
See all Perplexity alternatives → · See all Deep Lake alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Perplexity is currently shipping more aggressively (velocity 8.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Perplexity is currently shipping more aggressively (velocity 8.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other ai-assistants products to evaluate alongside.
Top Perplexity alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Perplexity alternatives" section above for the current picks, or visit /alternatives/perplexity for the full list with editorial commentary on each.
Top Deep Lake alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Deep Lake alternatives" section above for the current picks, or visit /alternatives/deeplake for the full list with editorial commentary on each.