Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Comparison · Infra & APIs
Cohere vs Merge
A side-by-side editorial comparison of Cohere and Merge — release velocity, themes, recent moves, and the top alternatives to consider.
Cohere vs Merge: at a glance
| Feature | Cohere | Merge |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 2.5 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | model-releases, agentic-reasoning, reranking, model-deprecation | unified api, agent handler, mcp connectors, ai gateway |
| Last editorial update | 13d ago | 13h ago |
| Website | Visit → | — |
What is Cohere?
Cohere is shipping a model a month and retiring the old ones just as briskly.
Cohere's changelog is almost entirely model announcements: Rerank 4.0 and Command A Reasoning in May, Command A+ later that month, North-Mini-Code in June, Transcribe Arabic in July. Two threads run through them — reasoning and agentic capability on the Command line, and a widening set of specialised models around it for ranking, code and speech. Running alongside is a steady retirement programme that hard-fails requests to older model IDs.
What is Merge?
Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.
Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.
Cohere vs Merge: editorial side-by-side
Cohere
2.5INFRA · APIS
Cohere is shipping a model a month and retiring the old ones just as briskly.
◆ Current state
Cohere's changelog is almost entirely model announcements: Rerank 4.0 and Command A Reasoning in May, Command A+ later that month, North-Mini-Code in June, Transcribe Arabic in July. Two threads run through them — reasoning and agentic capability on the Command line, and a widening set of specialised models around it for ranking, code and speech. Running alongside is a steady retirement programme that hard-fails requests to older model IDs.
◆ Where it's heading
The portfolio is splitting into a reasoning-heavy flagship line and purpose-built models beneath it, with the newer releases sized in explicit tiers rather than offered as one endpoint. Rerank 4.0's pro and fast variants show the pattern clearly: quality and latency become a customer choice instead of a vendor compromise. The deprecation cadence suggests Cohere is willing to keep the supported surface small, which keeps the catalog current but puts migration work on customers on a regular schedule.
◆ Prediction
Expect the tiered variant pattern to spread to more of the model line, and expect another retirement notice with a hard cutoff date as the newer generations settle. Several recent entries are captured with titles only, so the specifics of the Command A+ and North-Mini-Code releases are not visible here.
Merge
6.3INFRA · APIS
Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.
◆ Current state
Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.
◆ Where it's heading
The through-line is that Merge is repositioning from data plumbing to the layer agents pass through. Each week adds either reach (more connectors, more tools per connector, more models) or control (guardrails, per-project policy, access configuration). This window is reach-and-efficiency: the GitHub connector expanded to 145 tools, Outlook payloads were cut substantially, and Gateway guardrails became configurable per project rather than per account.
◆ Prediction
Expect the per-project granularity applied to guardrails to spread to the rest of Gateway's controls, and the connector catalog to keep absorbing hosted third-party MCP servers the way Axiom was added.
Alternatives to Cohere and Merge
Other Infra & APIs 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 Cohere or Merge.
DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
See all Cohere alternatives → · See all Merge alternatives →
Recent activity from Cohere and Merge
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoMergeGitHub connector hits 145 tools; Gateway adds per-project guardrails
- 19d agoMergeHundreds of generic MCP connectors land in Agent Handler ⚡
- 26d agoMergeLink setup flow becomes configurable per integration
- 1mo agoMergeEmbedded Routing Stack gives Gateway per-customer model controls
- 1mo agoMergeGateway breakout page for the week already covered by Week 2
- 1mo agoMergeUnified breakout page for the week already covered by Week 3
- 1mo agoCohereMeet Cohere Transcribe Arabic
- 2mo agoCohereAnnouncing Cohere’s North-Mini-Code-1.0
- 3mo agoCohereAnnouncing Cohere’s Command A+
- 3mo agoCohereCohere's Rerank v4.0 Model is Here! ⚡
- 3mo agoCohereAnnouncing Cohere's Command A Reasoning Model ⚡
- 4mo agoCohereRetirement of Embed v2.0 and Aya Expanse / Vision 8B
Frequently asked questions
What is the difference between Cohere and Merge?
They serve adjacent needs but don't currently overlap on shipped themes. Merge is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
Is Cohere better than Merge?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Merge is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Cohere?
Top Cohere alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cohere alternatives" section above for the current picks, or visit /alternatives/cohere for the full list with editorial commentary on each.
What are the best alternatives to Merge?
Top Merge alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Merge alternatives" section above for the current picks, or visit /alternatives/merge-dev for the full list with editorial commentary on each.