authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Buildkite and Oh Dear — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Buildkite | Oh Dear |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | ci-cd, github-actions-compat, hosted-agents, credential-scoping | uptime-monitoring, mcp, ai-agents, authorization |
| Last editorial update | 1d ago | 2d ago |
| Website | — | Visit → |
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.
The monitoring account is becoming something an agent operates, not just a dashboard someone reads.
Oh Dear is an uptime and site-health monitoring service shipping a dated changelog most weeks, with each release mixing new capability, security work and fixes. The MCP server is the thread running through all of it: monitor create, update and delete arrived in May, tag groups and notification routing in June, and the August release extends it across downtime, check summaries, domain intelligence, maintenance windows, check state, status page updates, notification destinations, scheduled tasks, Broken Links, Application Health and account management. Around that sit steady monitoring improvements — consecutive-failure thresholds for sitemap alerts, raw JSON bodies in HTTP checks, better handling of out-of-order scheduled-task pings.
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.
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.
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.
Oh Dear is an uptime and site-health monitoring service shipping a dated changelog most weeks, with each release mixing new capability, security work and fixes. The MCP server is the thread running through all of it: monitor create, update and delete arrived in May, tag groups and notification routing in June, and the August release extends it across downtime, check summaries, domain intelligence, maintenance windows, check state, status page updates, notification destinations, scheduled tasks, Broken Links, Application Health and account management. Around that sit steady monitoring improvements — consecutive-failure thresholds for sitemap alerts, raw JSON bodies in HTTP checks, better handling of out-of-order scheduled-task pings.
Two things are being built at once and they depend on each other. The MCP surface keeps widening until an assistant can run the account end to end, and the authorization model keeps being tightened to make that safe — API token scoping, permission checks on monitor-modifying tools, access controls on the new write tools, sessions invalidated on password change. Each release moves both. Underneath, the business plumbing is being tidied in public too: legacy pricing shown on the plan chooser, corrected affiliate terms, an agency-focused pricing structure, AI wizard placeholder monitors excluded from usage limits.
Expect the MCP tool surface to keep filling in the remaining corners of the product and the permission model to keep pace with it, and expect the November Slack connection deprecation already being warned about in-app to produce a migration release before then.
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 Oh Dear.
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Alert rate limits stop being per-source and start being per-tenant, by query.
The essay series keeps running ahead of the products it describes.
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
The 3.x line finally ships function: authenticated secret writes and render patches.
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
See all Buildkite alternatives → · See all Oh Dear alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp — within Infra & APIs. Buildkite is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Buildkite is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 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.
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.
Top Oh Dear alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Oh Dear alternatives" section above for the current picks, or visit /alternatives/ohdear for the full list with editorial commentary on each.