Port is a platform for building and operating agentic workflows with governance built in. As described in Do you really need a human in every loop?, its answer to when an agent needs a human is to make the approval a step in the workflow: the workflow runs, reaches the gate, and pauses for a human decision before anything irreversible happens.
What distinguishes the two kinds of gate it supports is where the decision comes from, not whether one exists. A Rule-Based Gate reads a condition the organisation wrote — the post’s example being an eligibility rule reading from real incident and service data, so that a low-severity incident on a non-critical service lets the remediation agent act alone. A Risk-Based Gate instead has an agent score the action, and Port is described as doing that against its context lake, tracing how far a change reaches through the connected graph to decide whether to let it run or pull in a human.
Capabilities
The context lake is the component both gates rest on: a connected graph of an organisation’s services, deployments, ownership and dependencies, from which rule-based conditions and risk scores both read. Because they read from one source, the post says the same workflow can let low-risk actions run and block high-risk ones without custom plumbing.
The handoff to a human is described as carrying context rather than just interrupting. In a Port incident workflow shown at PlatformCon, the workflow pauses at an approval gate and, on escalation, fires a coding agent node with the full incident context already loaded — the triage summary, the affected service, the recent deployment and the linked pull requests — so that the human and the agent work from the same picture instead of starting cold.
Adoption & Ecosystem
The post positions the platform as the answer to a problem it argues is structural rather than per-workflow: once a team accepts that it needs both kinds of gate, that each needs thresholds, tracing and safe fallbacks, and that both run on the same live context, hand-wiring them into every workflow stops being an option. Its stated consequence is that oversight stops being a tax on velocity, because a governed workflow becomes the easy one to build. That account comes from the vendor’s own blog, so the framing and the product are not separable here; the post also reports that when Port surveyed engineering leaders at one of its meetups, half the room said they still gate only code merges and pull requests.