Port

Port now offers External Interfaces, letting you build custom apps hosted anywhere where users sign in with Port and act with their own permissions, reading the Port context lake and triggering workflows. Previously there was no way to extend Port's RBAC into externally hosted apps without reimplementing permissions, so users keep their existing Port role and access without rebuilding authorization logic.

Matters for: Platform engineering teams building custom internal tools or AI-generated web apps (via Lovable, v0, or bolt.new through Port MCP) that need to read Port data and act under existing Port roles.

Port Workflows, the governed orchestration layer chaining agents, automations, business rules, and human approvals, is now generally available, alongside new abilities to sync and trigger Cursor cloud agents, trigger Azure DevOps pipelines, approve/fill workflow inputs from Slack, scope permissions to MCP agent invocations, and manage workflows as code via the Terraform provider. Array properties can now merge values from multiple integrations or manual edits instead of overwriting each other, and GitHub/GitLab integrations can now discover and catalog Agent Skills and plugin packages from repos.

Matters for: Relevant for platform teams building internal developer portals that need to govern AI agent execution alongside human approvals and CI/CD pipelines like GitHub Actions, GitLab, Jenkins, ArgoCD, and Azure DevOps.

Port AI can now plan and execute real platform changes such as creating blueprints, upserting entities, triggering workflows, and building dashboards, with per-tool approval controls and Ask/Plan/Build modes for review before execution; this release also adds Claude Managed Agents sync, cron-based workflow scheduling, self-service SSO setup, dynamic permission policies covering update/register/unregister actions, workflow ownership delegation via catalog permissions, Survey Intelligence for engineering surveys, and AI-guided org onboarding. None of these changes are breaking, so no existing configuration or workflow needs to be modified to continue working as before.

Matters for: Platform engineering teams building internal developer portals who need to delegate workflow and permission ownership to product teams while using AI agents like Claude or Cursor to manage catalog operations.

Port now lets teams build multi-step automation flows visually (Workflows Open Beta), create private catalog pages, and connect AI agents to external MCP servers like New Relic for use in chat and automations; it also adds GitLab CI/CD pipeline triggers from workflows, persistent AI chat history, thread-aware Slack AI with interactive forms, and a mapping apply feature that skips full resyncs. None of these changes are breaking, so existing workflows, integrations, and plugin code continue to work unchanged.

Matters for: Platform engineering teams running self-service developer portals who use GitLab CI/CD, Slack for incident response, and Cursor for AI-assisted coding across multiple engineering teams.