Merge vs Buildkite
Side-by-side trajectory, velocity, and editorial themes.
Merge is building an AI-infrastructure stack alongside its unified-API core, with Gateway emerging as a safety/governance layer.
Merge Unified continues a weekly cadence of API maintenance and connector expansion, with Oracle Fusion Cloud ERP launching for Accounting in beta. Merge Agent Handler — the MCP/agent-tools product — is shipping new connectors almost weekly and added Scoped Access Keys for least-privilege agent runtimes. Merge Gateway, the LLM gateway, just shipped Prompt Injection Protection, DLP, RBAC, audit trails, model pinning, and provider-free routing in back-to-back weeks.
Merge is no longer just a unified-API company. Two adjacent products — Agent Handler and Gateway — are getting the heaviest investment, while Unified gets steady connector and reliability work. The Gateway moves into safety and governance target enterprise AI deployments where native provider safety isn't enough. Agent Handler's connector pace suggests Merge wants to be the default tool-pack provider for agent builders.
Expect more Gateway governance features (custom DLP rules, broader vendor support, finer role-based controls) and continued weekly connector drops in Agent Handler — most likely targeting enterprise-SaaS gaps. The Unified roadmap may start incorporating agent-shaped endpoints, blurring lines between Unified and Agent Handler.
AI-agent skills and OAuth Token Exchange land — Buildkite is courting both Claude/Cursor users and security teams.
Buildkite is shipping in two strong directions at once. On platform/security: OAuth 2.0 Token Exchange (RFC 8693) replaces long-lived API tokens with IdP-minted short-lived ones, and per-user API rate limits stop one runaway script from starving an org's quota. On surface area: official Buildkite skills for Claude Code, Cursor and similar AI coding agents teach agents how to use the platform, plus broader GitHub event triggers for incremental Actions migration. Smaller UX work (new build page list view, queue search, cluster sort) rounds out a heavy ship cadence.
Two arcs are converging: lowering the on-ramp for teams migrating off GitHub Actions (more triggers, agent-friendly skills, cleaner UI) and meeting the security posture larger customers ask for in procurement (short-lived tokens, scoped per-user limits). The agent-skills release in particular signals Buildkite expects pipeline configuration to increasingly be authored or modified by AI agents, and is moving to teach them in Buildkite's own voice.
Expect more skills coverage across specific Buildkite features (dynamic pipelines, OIDC federation patterns) and follow-on auth work — OIDC-based agent authentication, finer scopes on exchanged tokens. The GitHub Actions migration push will likely add equivalents for less common triggers (deployments, workflow_dispatch) to remove remaining excuses to stay.
See more alternatives to Merge →
See more alternatives to Buildkite →