authentik
authentik 2026.8 ships: Actors, domain-joined Agents, and a push past browser-mediated SSO
Comparison · Infra & APIs
Knock vs Port
A side-by-side editorial comparison of Knock and Port — release velocity, themes, recent moves, and the top alternatives to consider.
Knock vs Port: at a glance
| Feature | Knock | Port |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 3.8 |
| Sparks · 30d | 1 | 1 |
| Top themes | notifications, developer-infrastructure, rbac, workflow-automation | agentic sdlc, internal developer portal, mcp, workflow automation |
| Last editorial update | 1d ago | 12d ago |
| Website | — | Visit → |
What is Knock?
Knock is hardening for enterprise buyers while its agent takes over the analysis work.
Knock ships weekly, in small, legible increments across three lanes: account governance (custom roles, passkeys), workflow primitives (wait-for-event, branch rebasing), and data ingress (Amplitude, Clay). The newest entry adds granular custom roles, which closes the last obvious gap in account-level access control. Alongside that, the in-product agent gained analytics, letting teams interrogate delivery performance without building reports.
What is Port?
Port AI graduated from answering questions about the catalog to changing it, with approval.
Port is an internal developer portal whose center of gravity has moved to Port AI. Over ten months it went from an open-beta chat assistant to an agent that plans and executes real platform changes — creating blueprints, upserting entities, triggering workflows — behind a plan the user approves first. The surrounding platform work is almost entirely extensibility: a public plugins repo, Custom Widgets, Workflows in open beta, and MCP connectors that pull external tools into the same chat.
Knock vs Port: editorial side-by-side
Knock
6.3INFRA · APIS
Knock is hardening for enterprise buyers while its agent takes over the analysis work.
◆ Current state
Knock ships weekly, in small, legible increments across three lanes: account governance (custom roles, passkeys), workflow primitives (wait-for-event, branch rebasing), and data ingress (Amplitude, Clay). The newest entry adds granular custom roles, which closes the last obvious gap in account-level access control. Alongside that, the in-product agent gained analytics, letting teams interrogate delivery performance without building reports.
◆ Where it's heading
Two arcs run in parallel. The infrastructure lane is buying enterprise credibility — roles, passkeys, audit-grade permissions — the checklist items that decide procurement rather than daily use. The data lane keeps widening what can trigger a workflow: product analytics from Amplitude, enriched rows from Clay, internal Slack channels as a destination. Together they push Knock from a notification API toward the messaging control plane, with the agent as the layer that explains what the plane did.
◆ Prediction
Expect the roles work to continue into audit logs or scoped API keys, since granular permissions without an activity trail is an incomplete enterprise story. More data sources are likely on the same cadence, with the CRM and warehouse categories the obvious remaining gaps.
Port
3.8INFRA · APIS
Port AI graduated from answering questions about the catalog to changing it, with approval.
◆ Current state
Port is an internal developer portal whose center of gravity has moved to Port AI. Over ten months it went from an open-beta chat assistant to an agent that plans and executes real platform changes — creating blueprints, upserting entities, triggering workflows — behind a plan the user approves first. The surrounding platform work is almost entirely extensibility: a public plugins repo, Custom Widgets, Workflows in open beta, and MCP connectors that pull external tools into the same chat.
◆ Where it's heading
The arc is assistant to gateway to executor. March made Port AI a front end for other vendors' tools via external MCP servers; June put a visual automation builder underneath it; July let the AI drive both, with Plan and Build modes and per-step traces. Each release widens what the agent may touch while keeping a human approval gate in front of it, and the extensibility work — plugins, widgets, bring-your-own LLM endpoint — exists so customers can extend the surface the agent operates on.
◆ Prediction
Expect the approval gate itself to become the product surface: policy governing which plans may execute unattended, tied to the Dynamic RBAC and permissions simulator already shipped. The step-by-step plans and per-step traces in the July release are the groundwork for granting scoped autonomy.
Alternatives to Knock and Port
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Knock or Port.
Rancher
Rancher's public feed is a build-tag stream: three branches bumped the same Go image on one afternoon
Buildkite
Buildkite keeps converting hand-rolled agent workarounds into first-class CI primitives.
Cursor
Cursor's agents stop waiting to be asked - they subscribe, and they hold a goal until it's done.
incident.io
Nexus does the diagnosis; the agent is now reaching into the status page too.
Warp
Warp turned its quarter of software-factory essays into infrastructure you can buy.
Recent activity from Knock and Port
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoKnockCustom roles and permissions
- 7d agoKnockPower internal Slack alerts
- 8d agoKnockCategory + tag management
- 12d agoPortPort AI Builder plans and executes catalog changes with approval ⚡
- 14d agoKnockAmplitude data source
- 21d agoKnockAnalytics in the Knock agent ⚡
- 22d agoKnockWait for event function
- 1mo agoPortWorkflows hits open beta; AI agents connect external MCP servers
- 2mo agoPortPublic plugins repo opens Port to community contributions
- 3mo agoPortCustom Widgets run your own UI inside Port; BYO OpenAI endpoint
- 4mo agoPortMCP Connectors turn Port AI into a gateway for external tools ⚡
- 5mo agoPortRun Claude in your own Azure; RBAC gets a UI and simulator
Frequently asked questions
What is the difference between Knock and Port?
They serve adjacent needs but don't currently overlap on shipped themes. Knock is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Knock better than Port?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Knock is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Knock?
Top Knock alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Knock alternatives" section above for the current picks, or visit /alternatives/knock for the full list with editorial commentary on each.
What are the best alternatives to Port?
Top Port alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Port alternatives" section above for the current picks, or visit /alternatives/port for the full list with editorial commentary on each.