Knock vs Buildkite
Side-by-side trajectory, velocity, and editorial themes.
Knock is rewiring notifications infrastructure to be configured by agents, not just developers.
Knock is methodically rebuilding its primitives — audiences, layouts, reusable steps, in-app guides — so they're versioned, environment-promotable, and addressable from an agent in addition to the dashboard and CLI. The recent run shows a clear pattern: each new feature ships with at least one agent-accessible path. Underneath, the engineering surface is also tightening, with reusable request input schemas making composability less guesswork.
Knock is positioning its platform as agent-buildable messaging infrastructure rather than just a developer SDK. Skills, dynamic audiences, and schema'd reusable steps are the building blocks of a future where a product team agent (or Knock's own) can spin up an entire notification flow without a developer touching code. The Layouts 2.0 refresh and Guides toolbar work in parallel to harden the human surfaces that remain.
Expect Knock to publish a more opinionated agent surface — likely an MCP-style server or an in-product agent that orchestrates skills against dynamic audiences. The reusable-input-schemas release is the kind of plumbing that precedes a 'build a workflow from a prompt' demo, so a higher-level natural-language workflow composer is the most probable next move.
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 Knock →
See more alternatives to Buildkite →