Merge vs Buildkite
Side-by-side trajectory, velocity, and editorial themes.
Merge grinds out weekly breadth — more integrations, fields, and reliability across its unified APIs
Merge's cadence is steady, incremental expansion of unified API coverage. Recent weeks add accounting filters and Sage Intacct/Xero/NetSuite mapping enhancements, Xero attachment uploads, SharePoint drive and file support, QuickBooks invoice webhooks, and edge-case and reliability fixes across ATS, CRM, chat, and file storage.
There is no single headline feature; the strategy is coverage depth. Each week broadens field mappings, object URLs, and integration reliability, which compounds into a wider, more dependable normalization layer. The heavy accounting focus signals that vertical as the current priority.
Expect the same weekly rhythm: more per-integration mappings, additional attachment and object-URL support, and expansion of newer connectors like Oracle Fusion Cloud ERP. No directional pivot is visible in these entries.
Buildkite widens its API surface for agent-driven CI debugging and observability
Buildkite's recent releases cluster around one theme: exposing more of the CI runtime through APIs. Richer REST job and agent objects, per-job performance metrics, and MCP server tooling all aim at automated and agent-driven consumers, alongside a security fix and an infrastructure notice.
The platform is being reshaped for programmatic and agentic use — surfacing signal_reason and runner context so automation can tell infrastructure failures from code failures, adding job-level CPU/memory/disk metrics, and splitting jobs from builds for large-matrix querying. The MCP investment (elsewhere in the feed) is the same bet from another angle.
Expect the REST and GraphQL surfaces to keep expanding toward machine consumers, with the MCP server becoming the primary interface for automated build triage.
See more alternatives to Merge →
See more alternatives to Buildkite →