Interface builder
The interface builder lets you create interactive operational surfaces — views of your catalog where the right people can see what matters and act on it directly, without leaving the page.
Some examples include:
- A deployment dashboard that shows every service's current version, health score, and on-call engineer — with a Deploy button that opens a form and triggers the deployment workflow.
- An incident response view: every open incident, its owning team, blast radius graph, and a Page on-call button right next to it.
- A team health page: scorecard compliance, open PRs, lead time trend, and a Request exception button for the one service that's falling behind.
⬆ The
AI Agent Control Centerdashboard as displayed in Port's demo portal
Pages and dashboards
Your catalog is composed of pages. Each page is either a catalog view (a table of entities filtered and grouped as you wish) or a dashboard (a freeform canvas of widgets). Every entity also has its own page, auto-created when the entity is ingested, with its own dashboard tab you can customize.
Widgets range from charts, tables, and scorecards to iframes embedding external tools. Pages can be scoped by team or role so each audience sees exactly what they need.
Actions embedded in surfaces
The part that turns a dashboard into a control plane: action card widgets let you embed any self-service workflow directly into a page as a button. A developer on a service entity page can provision a feature flag, trigger a deployment, or file an incident — without navigating away.
The workflows those buttons trigger are the same governed, audited workflows defined in Workflows & tools. Nothing bypasses the execution layer.
Notifications and AI
The Slack app delivers real-time alerts and lets your team respond to events without leaving their communication platform. The AI chat widget embeds a Port AI agent directly into any dashboard, giving any team a context-aware assistant right where they work.