authentik
authentik 2026.8 ships: Actors, domain-joined Agents, and a push past browser-mediated SSO
A side-by-side editorial comparison of Buildkite and missSBM — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Buildkite | missSBM |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 8.8 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | ci-cd, developer-tools, mcp, observability | r-package, network-analysis, stochastic-block-model, missing-data |
| Last editorial update | 3h ago | 1d ago |
| Website | — | Visit → |
Buildkite keeps converting hand-rolled agent workarounds into first-class CI primitives.
Buildkite is shipping on two fronts. For agents, the MCP server gained list_tests for suite-wide reliability and duration metrics, and the Test Engine API returns the same aggregates behind a version header. For humans, a native checkout block moved sparse clones, shallow depth and skip-checkout out of plugins and into pipeline YAML, agents can ship job logs to an OpenTelemetry collector, and an organization-wide banner now says when GitHub API rate limits - not Buildkite - are holding up pull request status.
missSBM returns after four dormant years with a stricter API and a new refinement step.
The package fits stochastic block models to networks with missing data, covering both missing-at-random and informative sampling designs. After a run of releases from 2019 to 2022, the feed goes quiet until this year's 1.1.0, which breaks the control interface, exposes the block split and merge operations as testable instance methods, and adds a node-swap refinement pass that runs after variational convergence.
Buildkite is shipping on two fronts. For agents, the MCP server gained list_tests for suite-wide reliability and duration metrics, and the Test Engine API returns the same aggregates behind a version header. For humans, a native checkout block moved sparse clones, shallow depth and skip-checkout out of plugins and into pipeline YAML, agents can ship job logs to an OpenTelemetry collector, and an organization-wide banner now says when GitHub API rate limits - not Buildkite - are holding up pull request status.
Buildkite is arguing that CI should be forge-independent, and backing it with coverage: GitHub, GitLab, Bitbucket, and now Cursor's Origin, where it shipped as a launch partner on day one. The agent-facing work follows one pattern - remove the workaround automation used to need, so aggregated test metrics replace assembling individual runs and a rate-limit banner replaces guessing why a status never arrived. Each release turns a behavior teams hand-rolled into a supported primitive.
The read side of the MCP server is now largely covered, so expect write-side tools next - retrying jobs, unblocking builds, editing pipelines from an agent - following the pattern the REST expansion established.
The package fits stochastic block models to networks with missing data, covering both missing-at-random and informative sampling designs. After a run of releases from 2019 to 2022, the feed goes quiet until this year's 1.1.0, which breaks the control interface, exposes the block split and merge operations as testable instance methods, and adds a node-swap refinement pass that runs after variational convergence.
The new release is maintenance-driven in the best sense: it targets the parts of the codebase that were hard to test or easy to misuse. Replacing free-form control lists with a function of named, defaulted arguments turns silent typos into errors, and pulling the exploration logic out of the collection class makes the search algorithm independently testable without changing it. The polish step addresses a known weakness, reaching individually misclassified nodes that split and merge moves cannot fix.
Given the gap before this release, the near-term question is whether the cadence resumes at all; the refactoring it contains would support further algorithmic work if it does.
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 missSBM.
authentik 2026.8 ships: Actors, domain-joined Agents, and a push past browser-mediated SSO
Rancher's public feed is a build-tag stream: three branches bumped the same Go image on one afternoon
Cursor's agents stop waiting to be asked - they subscribe, and they hold a goal until it's done.
Nexus does the diagnosis; the agent is now reaching into the status page too.
Warp turned its quarter of software-factory essays into infrastructure you can buy.
Okta's developer blog is a Cross App Access campaign, now diluted by advocacy-team storytelling.
See all Buildkite alternatives → · See all missSBM alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Buildkite is currently shipping more aggressively (velocity 8.8 vs 2.5), 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 8.8 vs 2.5), 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 missSBM alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "missSBM alternatives" section above for the current picks, or visit /alternatives/misssbm for the full list with editorial commentary on each.