Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Comparison · Infra & APIs
Port vs WorkOS
A side-by-side editorial comparison of Port and WorkOS — release velocity, themes, recent moves, and the top alternatives to consider.
Port vs WorkOS: at a glance
| Feature | Port | WorkOS |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 3.8 | 8.8 |
| Sparks · 30d | 1 | 2 |
| Top themes | agentic sdlc, internal developer portal, mcp, workflow automation | identity, authentication, ai-agents, scim |
| Last editorial update | 11d ago | 13h ago |
| Website | Visit → | — |
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.
What is WorkOS?
WorkOS is building identity for agents while quietly fixing the sign-up funnel.
WorkOS ships several small entries a week, and August splits cleanly in two. One half is authentication housekeeping for human users: an Android SDK, deliverability checks that reject undeliverable addresses at sign-up, invitation acceptance counting as email verification, and a reversible SCIM proxy for migrating directory connections without downtime. The other half is agent infrastructure — Agent Registration via the auth.md protocol, and the Pipes Token Proxy that calls third-party APIs on a user's behalf without the application ever touching their token.
Port vs WorkOS: editorial side-by-side
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.
WorkOS
8.8INFRA · APIS
WorkOS is building identity for agents while quietly fixing the sign-up funnel.
◆ Current state
WorkOS ships several small entries a week, and August splits cleanly in two. One half is authentication housekeeping for human users: an Android SDK, deliverability checks that reject undeliverable addresses at sign-up, invitation acceptance counting as email verification, and a reversible SCIM proxy for migrating directory connections without downtime. The other half is agent infrastructure — Agent Registration via the auth.md protocol, and the Pipes Token Proxy that calls third-party APIs on a user's behalf without the application ever touching their token.
◆ Where it's heading
The agent work is the strategic line. Registration gives an agent an identity of its own instead of a borrowed human session; the token proxy means an application acting for a user never holds the credential. Together they describe a stack where an agent can be authorized, audited and revoked as a first-class principal. The human-auth releases are conversion and migration work — the deliverability check and SCIM Bridge both remove reasons a customer stalls — which is what a developer-infrastructure company does while its next category is still forming.
◆ Prediction
Registration and the token proxy leave scoping and revocation as the visible gaps, so expect per-agent permissions or consent surfaces next. Whether auth.md gains adoption beyond WorkOS is not something these entries can answer.
Alternatives to Port and WorkOS
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 Port or WorkOS.
DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
Recent activity from Port and WorkOS
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoWorkOSAndroid SDK
- 2d agoWorkOSHigher quality sign-ups with email deliverability checks
- 5d agoWorkOSMigrate SCIM Connections with SCIM Bridge
- 6d agoWorkOSAccepted invitations count as email verification
- 11d agoPortPort AI Builder plans and executes catalog changes with approval ⚡
- 13d agoWorkOSPipes Token Proxy ⚡
- 15d agoWorkOSAgent Registration ⚡
- 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 Port and WorkOS?
They serve adjacent needs but don't currently overlap on shipped themes. WorkOS is currently shipping more aggressively (velocity 8.8 vs 3.8), with 2 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 Port better than WorkOS?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. WorkOS is currently shipping more aggressively (velocity 8.8 vs 3.8), with 2 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 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.
What are the best alternatives to WorkOS?
Top WorkOS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "WorkOS alternatives" section above for the current picks, or visit /alternatives/workos for the full list with editorial commentary on each.