Port vs WorkOS
Side-by-side trajectory, velocity, and editorial themes.
Port turns its AI catalog into an automation platform as Workflows hits open beta
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.
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.
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.
WorkOS ships three new surfaces in a week, pushing into front-end widgets and agent-run admin.
WorkOS is an enterprise identity and auth infrastructure provider, best known for AuthKit, SSO, directory sync, and audit logs. The changelog shows an unusually dense shipping burst: three distinct new product surfaces in a single week, the Widgets API, a Management MCP server, and an API Gateway, layered on top of steady AuthKit feature work like step-up authentication, waitlists, and an Astro integration.
Two directions are visible. First, AuthKit is growing from a backend auth library into a fuller front-end toolkit, adding client widgets, framework SDKs, and richer session flows. Second, the platform is becoming programmable by agents and unified at the edge, via the MCP server and the API Gateway. WorkOS is moving up the stack from backend primitives toward client UI and agent-driven administration.
Expect more AuthKit framework integrations and additional agent-facing tooling built on the MCP server, plus broadening coverage for the newer Widgets API and API Gateway. The pace suggests WorkOS is racing to own both the front-end auth UI layer and the agent-administration layer at once.
See more alternatives to Port →
See more alternatives to WorkOS →