← Back to home
Comparison · Infra & APIs

Cohere vs WorkOS

Side-by-side trajectory, velocity, and editorial themes.

C
Cohere
INFRA · APIS
6.3

Cohere prunes legacy models while pushing into speech and code

◆ Current state

Cohere is refreshing and broadening its enterprise model lineup rather than iterating a single stack. In the observable window it has shipped a new flagship tier (Command A+), started a first-party speech-to-text line (Transcribe, now extended to Arabic), and released a code-focused model tied to its North platform (North-Mini-Code) — while retiring older Embed, Aya, and Command versions.

◆ Where it's heading

The pattern is consolidate-and-expand: retire legacy models on a fixed schedule and push customers onto the current generation, while adding new capability surfaces beyond text — audio/ASR and code. The multilingual and Arabic transcription work signals a deliberate reach into non-English enterprise markets rather than chasing frontier-model benchmarks head-on.

◆ Prediction

Expect further language and modality expansion of the Transcribe line and more North-tied specialized models, paired with continued retirement of older Command and Embed versions as the catalog narrows.

W
WorkOS
INFRA · APIS
7.5

WorkOS ships three new surfaces in a week, pushing into front-end widgets and agent-run admin.

◆ Current state

WorkOS is an enterprise identity and auth infrastructure provider, best known for AuthKit, SSO, directory sync, and audit logs. The changelog shows an unusually dense shipping burst: three distinct new product surfaces in a single week, the Widgets API, a Management MCP server, and an API Gateway, layered on top of steady AuthKit feature work like step-up authentication, waitlists, and an Astro integration.

◆ Where it's heading

Two directions are visible. First, AuthKit is growing from a backend auth library into a fuller front-end toolkit, adding client widgets, framework SDKs, and richer session flows. Second, the platform is becoming programmable by agents and unified at the edge, via the MCP server and the API Gateway. WorkOS is moving up the stack from backend primitives toward client UI and agent-driven administration.

◆ Prediction

Expect more AuthKit framework integrations and additional agent-facing tooling built on the MCP server, plus broadening coverage for the newer Widgets API and API Gateway. The pace suggests WorkOS is racing to own both the front-end auth UI layer and the agent-administration layer at once.

See more alternatives to Cohere
See more alternatives to WorkOS