← Back to home
Comparison · Infra & APIs

Port vs Buildkite

Side-by-side trajectory, velocity, and editorial themes.

P
Port
INFRA · APIS
6.3

Port turns its AI catalog into an automation platform as Workflows hits open beta

◆ Current state

Port is an internal developer portal that has spent 2026 turning its software catalog into an AI-and-automation platform. Recent months added an MCP gateway (external MCP servers into Port AI), BYO/OpenAI-compatible LLM endpoints, an Azure Anthropic provider, Skills and Memory for its AI assistant, and a public plugins repo. June's headline is Workflows reaching Open Beta — a visual, node-based builder for self-service automations.

◆ Where it's heading

Two arcs are converging: Port AI as an open, model-agnostic gateway (external MCP, any OpenAI-compatible endpoint, Azure-hosted Claude, Skills/Memory) and Workflows as a visual automation layer on top of the catalog. The steady monthly 'Big' feature and the plugins ecosystem signal Port positioning as the automation and agentic-operations hub for platform-engineering teams, not just a catalog of services.

◆ Prediction

Workflows likely moves from Open Beta toward GA with more triggers and actions, while Port AI keeps expanding its connector and model surface — the two being stitched into one agentic self-service experience.

B
Buildkite
INFRA · APIS
6.3

Buildkite widens its API surface for agent-driven CI debugging and observability

◆ Current state

Buildkite's recent releases cluster around one theme: exposing more of the CI runtime through APIs. Richer REST job and agent objects, per-job performance metrics, and MCP server tooling all aim at automated and agent-driven consumers, alongside a security fix and an infrastructure notice.

◆ Where it's heading

The platform is being reshaped for programmatic and agentic use — surfacing signal_reason and runner context so automation can tell infrastructure failures from code failures, adding job-level CPU/memory/disk metrics, and splitting jobs from builds for large-matrix querying. The MCP investment (elsewhere in the feed) is the same bet from another angle.

◆ Prediction

Expect the REST and GraphQL surfaces to keep expanding toward machine consumers, with the MCP server becoming the primary interface for automated build triage.

See more alternatives to Port
See more alternatives to Buildkite