authentik
authentik 2026.8 ships: Actors, domain-joined Agents, and a push past browser-mediated SSO
Comparison · Infra & APIs
Merge vs Port
A side-by-side editorial comparison of Merge and Port — release velocity, themes, recent moves, and the top alternatives to consider.
Merge vs Port: at a glance
| Feature | Merge | Port |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 3.8 |
| Sparks · 30d | 1 | 1 |
| Top themes | unified api, agent handler, mcp connectors, ai gateway | agentic sdlc, internal developer portal, mcp, workflow automation |
| Last editorial update | 1d ago | 12d ago |
| Website | — | Visit → |
What is Merge?
Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.
Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.
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.
Merge vs Port: editorial side-by-side
Merge
6.3INFRA · APIS
Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.
◆ Current state
Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.
◆ Where it's heading
The through-line is that Merge is repositioning from data plumbing to the layer agents pass through. Each week adds either reach (more connectors, more tools per connector, more models) or control (guardrails, per-project policy, access configuration). This window is reach-and-efficiency: the GitHub connector expanded to 145 tools, Outlook payloads were cut substantially, and Gateway guardrails became configurable per project rather than per account.
◆ Prediction
Expect the per-project granularity applied to guardrails to spread to the rest of Gateway's controls, and the connector catalog to keep absorbing hosted third-party MCP servers the way Axiom was added.
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 Merge 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 Merge 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 Merge and Port
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoPortPort AI Builder plans and executes catalog changes with approval ⚡
- 13d agoMergeGitHub connector hits 145 tools; Gateway adds per-project guardrails
- 20d agoMergeHundreds of generic MCP connectors land in Agent Handler ⚡
- 27d agoMergeLink setup flow becomes configurable per integration
- 1mo agoMergeEmbedded Routing Stack gives Gateway per-customer model controls
- 1mo agoMergeGateway breakout page for the week already covered by Week 2
- 1mo agoMergeUnified breakout page for the week already covered by Week 3
- 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 Merge and Port?
They serve adjacent needs but don't currently overlap on shipped themes. Merge 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 Merge better than Port?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Merge 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 Merge?
Top Merge alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Merge alternatives" section above for the current picks, or visit /alternatives/merge-dev 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.