Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Comparison · Infra & APIs
Buildkite vs Merge
A side-by-side editorial comparison of Buildkite and Merge — release velocity, themes, recent moves, and the top alternatives to consider.
Buildkite vs Merge: at a glance
| Feature | Buildkite | Merge |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 8.8 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | ci-cd, mcp, agents, observability | unified api, agent handler, mcp connectors, ai gateway |
| Last editorial update | 1d ago | 14h ago |
| Website | — | — |
What is Buildkite?
Buildkite is rebuilding CI as something agents drive, not just humans.
Buildkite's recent releases split in two: MCP tooling for agents - list_tests, wait_for_build, compliance with the stateless MCP spec - and broader REST/GraphQL coverage so setup, governance, and troubleshooting can run headless. Conventional CI work continues underneath, with checkout configuration in pipeline YAML and OpenTelemetry job log export. The framing on nearly every note is what an agent can now do without a human in the loop.
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.
Buildkite vs Merge: editorial side-by-side
Buildkite
8.8INFRA · APIS
Buildkite is rebuilding CI as something agents drive, not just humans.
◆ Current state
Buildkite's recent releases split in two: MCP tooling for agents - list_tests, wait_for_build, compliance with the stateless MCP spec - and broader REST/GraphQL coverage so setup, governance, and troubleshooting can run headless. Conventional CI work continues underneath, with checkout configuration in pipeline YAML and OpenTelemetry job log export. The framing on nearly every note is what an agent can now do without a human in the loop.
◆ Where it's heading
Buildkite is arguing that CI should be forge-independent, and it is now backing that with coverage: GitHub, GitLab, Bitbucket, and as of this week Cursor's Origin, where it shipped as a launch partner on day one. On the agent side the pattern is removing the workarounds automation used to need - a wait tool instead of a polling loop, aggregated test metrics instead of assembling individual runs, an early failure signal instead of waiting for a job to exit. Each release converts a hand-rolled agent behavior into a first-class primitive.
◆ Prediction
The read side of the MCP server is now largely covered, so expect write-side tools next - retrying jobs, unblocking builds, creating or editing pipelines from an agent - following the same pattern the REST expansion just established.
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 Buildkite 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 Buildkite 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 Buildkite alternatives → · See all Merge alternatives →
Recent activity from Buildkite and Merge
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoBuildkiteBuildkite is a Cursor Origin launch partner
- 7d agoBuildkiteBuildkite MCP Server can now find your slowest and flakiest tests
- 12d agoMergeGitHub connector hits 145 tools; Gateway adds per-project guardrails
- 13d agoBuildkiteAnalyze test reliability and performance with the Test Engine API
- 13d agoBuildkiteCustomize Git checkout behavior directly in pipeline YAML
- 14d agoBuildkiteMore Buildkite workflows are available through APIs
- 14d agoBuildkiteSend job logs to your OpenTelemetry collector
- 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
Frequently asked questions
What is the difference between Buildkite and Merge?
They serve adjacent needs but don't currently overlap on shipped themes. Buildkite is currently shipping more aggressively (velocity 8.8 vs 6.3), with 0 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Buildkite better than Merge?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Buildkite is currently shipping more aggressively (velocity 8.8 vs 6.3), with 0 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Buildkite?
Top Buildkite alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Buildkite alternatives" section above for the current picks, or visit /alternatives/buildkite 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.