Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Comparison · Infra & APIs
Logstash vs Merge
A side-by-side editorial comparison of Logstash and Merge — release velocity, themes, recent moves, and the top alternatives to consider.
Logstash vs Merge: at a glance
| Feature | Logstash | Merge |
|---|---|---|
| Sector | Infra & APIs, Analytics | Infra & APIs |
| Velocity score | 3.3 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | observability, elastic-stack, ingest-pipeline, performance | unified api, agent handler, mcp connectors, ai gateway |
| Last editorial update | 3mo ago | 14h ago |
| Website | Visit → | — |
What is Logstash?
PQ compression and ES|QL preview land while weekly plugin churn drives the release cadence.
Logstash is in a steady maintenance phase across the 9.0–9.3 lines, with most weekly releases dominated by plugin dependency bumps (Netty, Avro, kotlin-stdlib) and small fixes. The substantive 9.x work — Persistent Queue compression via ZSTD, batch-size metrics, and ES|QL support in Technical Preview for the Elasticsearch input/filter — represents real capability gains for operators tuning throughput and storage. Security and credential-handling hygiene (sasl_jaas_config redaction, encoded API-key formats) shows up consistently across plugin updates.
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.
Logstash vs Merge: editorial side-by-side
Logstash
3.3INFRA · APISANALYTICS
PQ compression and ES|QL preview land while weekly plugin churn drives the release cadence.
◆ Current state
Logstash is in a steady maintenance phase across the 9.0–9.3 lines, with most weekly releases dominated by plugin dependency bumps (Netty, Avro, kotlin-stdlib) and small fixes. The substantive 9.x work — Persistent Queue compression via ZSTD, batch-size metrics, and ES|QL support in Technical Preview for the Elasticsearch input/filter — represents real capability gains for operators tuning throughput and storage. Security and credential-handling hygiene (sasl_jaas_config redaction, encoded API-key formats) shows up consistently across plugin updates.
◆ Where it's heading
The product is consolidating its role as the configurable ingest tier of the Elastic stack rather than chasing new categories. Investment is concentrated on operational efficiency — PQ compression, average batch metrics, JDBC concurrency lifts — and on tightening integration with newer Elasticsearch capabilities like ES|QL. Plugin maintenance burden is high but treated as first-class, suggesting the team has accepted the long tail of integrations as the durable surface area.
◆ Prediction
Expect ES|QL support to graduate from Technical Preview to GA in the next minor, and PQ compression to become the default once the rollback-barrier risk has aged out. Watch for further telemetry surfaces aimed at sizing — the batch-metrics work points toward a guided-tuning story.
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 Logstash 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 Logstash 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 Logstash alternatives → · See all Merge alternatives →
Recent activity from Logstash 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
- 4mo agoLogstashRelease notes index update (no shipped change)
- 4mo agoLogstashKafka Output regression fixed for sasl_jaas_config
- 4mo agoLogstashSecurity advisories pointer for 9.3.3
- 4mo agoLogstashElasticsearch Output - 12.1.3
- 4mo agoLogstashLogstash seizes 9.x: PQ compression, batch metrics, ES|QL preview ⚡
- 4mo agoLogstashAzure_event_hubs Input - 1.5.5
Frequently asked questions
What is the difference between Logstash and Merge?
They serve adjacent needs but don't currently overlap on shipped themes. Merge is currently shipping more aggressively (velocity 6.3 vs 3.3), 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 Logstash 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 3.3), 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 Logstash?
Top Logstash alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Logstash alternatives" section above for the current picks, or visit /alternatives/logstash 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.