authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Comparison · Infra & APIs
Buildkite vs Mergify
A side-by-side editorial comparison of Buildkite and Mergify — release velocity, themes, recent moves, and the top alternatives to consider.
Buildkite vs Mergify: at a glance
| Feature | Buildkite | Mergify |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | ci-cd, github-actions-compat, hosted-agents, credential-scoping | merge-queue, ci-automation, github, stacked-prs |
| Last editorial update | 1d ago | 5d ago |
| Website | — | Visit → |
What is Buildkite?
Buildkite is prying CI loose from the git forge while shrinking what an agent is trusted with.
Three threads run through the window. Buildkite keeps decoupling CI from the git forge: GitHub Actions workflows run unchanged in a public-preview plugin that now handles reusable workflows, Docker-based actions and service containers, and Buildkite shipped as a Cursor Origin launch partner alongside GitHub, GitLab and Bitbucket. Credentials are getting narrower — stack-managed ephemeral agents now register with a fifteen-minute job acquisition token scoped to one named job instead of the cluster agent token. And hosted-agent access keeps widening: after desktop and terminal access for macOS, the CLI's bk job ssh now reaches running Linux hosted jobs.
What is Mergify?
Mergify's queue learned to merge stacked pull requests, then spent August tightening the edges.
Mergify automates merge queues for GitHub, and August was a mix of one real capability and a batch of contract cleanup. The queue can now merge GitHub-native stacked pull requests in order, speculative-check budgets apply per lane across dynamic scope sets, and conditions can match on whether a pull request came from a fork. Alongside that, the badge API was removed, pagination stopped advertising first and last links, and author-run commands were restricted to fork pull requests by default.
Buildkite vs Mergify: editorial side-by-side
Buildkite
6.3INFRA · APIS
Buildkite is prying CI loose from the git forge while shrinking what an agent is trusted with.
◆ Current state
Three threads run through the window. Buildkite keeps decoupling CI from the git forge: GitHub Actions workflows run unchanged in a public-preview plugin that now handles reusable workflows, Docker-based actions and service containers, and Buildkite shipped as a Cursor Origin launch partner alongside GitHub, GitLab and Bitbucket. Credentials are getting narrower — stack-managed ephemeral agents now register with a fifteen-minute job acquisition token scoped to one named job instead of the cluster agent token. And hosted-agent access keeps widening: after desktop and terminal access for macOS, the CLI's bk job ssh now reaches running Linux hosted jobs.
◆ Where it's heading
The positioning is stated outright in the Origin post — your CI platform should not depend on your git forge — and the GitHub Actions compatibility work aims the same argument at the incumbent, letting teams run existing workflows before committing to a rewrite. Underneath, Buildkite is rebuilding hosted agents into something you can reach into interactively: terminal, then desktop, now SSH on Linux, all through one CLI. The credential work runs the other direction, moving from long-lived cluster tokens toward per-job issuance, with the Kubernetes stack already defaulting to it.
◆ Prediction
Custom stack implementations are the likely next surface to adopt job acquisition tokens, since the Stacks API already exposes issuance and the Kubernetes stack defaults to it. Expect the remaining hosted-agent access gaps to close the same way — Linux desktop access is the obvious symmetry left after SSH.
Mergify
6.3INFRA · APIS
Mergify's queue learned to merge stacked pull requests, then spent August tightening the edges.
◆ Current state
Mergify automates merge queues for GitHub, and August was a mix of one real capability and a batch of contract cleanup. The queue can now merge GitHub-native stacked pull requests in order, speculative-check budgets apply per lane across dynamic scope sets, and conditions can match on whether a pull request came from a fork. Alongside that, the badge API was removed, pagination stopped advertising first and last links, and author-run commands were restricted to fork pull requests by default.
◆ Where it's heading
Two threads. The queue is absorbing workflows that used to sit outside it - stacked pull requests, flaky-test detection and rerunning within a CI budget - which pushes Mergify from a merge gate toward owning the whole pre-merge pipeline. The other thread is a deliberate narrowing of surface: deprecated endpoints removed, the github_actions action marked for removal in March 2027, default command permissions tightened around forks. That is a product trimming what it maintains so the queue can take on more.
◆ Prediction
Expect more of the pre-merge pipeline to move inside the queue on the flaky-test pattern, and further deprecations of automation that overlaps with what GitHub Actions now does natively.
Alternatives to Buildkite and Mergify
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 Mergify.
incident.io
Alert rate limits stop being per-source and start being per-tenant, by query.
Warp
The essay series keeps running ahead of the products it describes.
Node-RED
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
werf
The 3.x line finally ships function: authenticated secret writes and render patches.
Infisical
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
See all Buildkite alternatives → · See all Mergify alternatives →
Recent activity from Buildkite and Mergify
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoBuildkiteSSH into Linux hosted jobs from the Buildkite CLI
- 2d agoBuildkiteJob acquisition tokens for ephemeral agents
- 6d agoBuildkiteAgent names using `%n` now receive a random suffix
- 7d agoBuildkiteBlock and input steps get their own Waiting for input group
- 8d agoBuildkiteGitHub Actions compatibility now runs reusable workflows, Docker actions and service containers
- 8d agoBuildkiteAdditional GitHub App permissions for GitHub Actions workflows
- 8d agoMergifyPer-lane check capacity for dynamic scopes
- 8d agoMergifyPagination drops the first and last links
- 8d agoMergifyRepository badge API removed
- 8d agoMergifyClearer reason when the merge queue can't create the draft pull request
- 21d agoMergifyMerge GitHub stacked pull requests with the merge queue ⚡
- 22d agoMergifyNew from-fork condition attribute
Frequently asked questions
What is the difference between Buildkite and Mergify?
They serve adjacent needs but don't currently overlap on shipped themes. Buildkite and Mergify are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Buildkite better than Mergify?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Buildkite and Mergify are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 Mergify?
Top Mergify alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Mergify alternatives" section above for the current picks, or visit /alternatives/mergify for the full list with editorial commentary on each.