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 RSA — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Buildkite | RSA |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 8.8 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | ci-cd, developer-tools, mcp, observability | response-surface-analysis, psychometrics, lavaan, plotting |
| Last editorial update | 1h ago | 3h 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.
Four years quiet, then two releases ninety seconds apart, both about drawing better plots
RSA implements response surface analysis for congruence questions in psychology, built on lavaan. After four and a half years of silence the maintainer pushed 0.10.6 and 0.10.8 within ninety seconds of each other on 2 October 2025, so the feed's version sequence is a backfill of accumulated work rather than two separate release events. Both are plotting releases: user-defined lines and points on the surface, stilts for selected data points, and separate control of point fill and border colour.
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.
RSA implements response surface analysis for congruence questions in psychology, built on lavaan. After four and a half years of silence the maintainer pushed 0.10.6 and 0.10.8 within ninety seconds of each other on 2 October 2025, so the feed's version sequence is a backfill of accumulated work rather than two separate release events. Both are plotting releases: user-defined lines and points on the surface, stilts for selected data points, and separate control of point fill and border colour.
The statistical core has been stable since 0.10.0 in 2020, which added control variables, pooled centering and a corrected AICc. Everything since is either plot customisation or a reaction to a dependency — lavaan model comparison, rgl deprecations, tkrplot on Apple Silicon, the ggplot2 fill aesthetic. This is a mature method implementation in maintenance, where the visible work is making its surface plots publishable.
Further releases are most likely dependency reactions, with rgl and ggplot2 the two that have repeatedly forced changes, and plot customisation arriving in batches whenever the maintainer returns to the package.
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 RSA.
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 RSA 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 0.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 8.8 vs 0.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 RSA alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "RSA alternatives" section above for the current picks, or visit /alternatives/rsa for the full list with editorial commentary on each.