WorkOS
An infrastructure provider in the enterprise identity and access management (IAM) space that offers SaaS companies capabilities such as single sign-on (SSO), directory synchronization, and audit logging. It serves as the identity authentication infrastructure for numerous B2B software companies.
Core Facts
Timeline (last 90 days)
WorkOS was originally positioned to help SaaS products quickly integrate enterprise-grade identity capabilities such as SSO and directory sync.
WorkOS was selected for the 2026-27 Cyber60 list.
WorkOS launched the User Groups feature, allowing developers to assign roles to user groups rather than managing individuals one by one.
In multi-role mode, the roles corresponding to the various groups a user belongs to stack and take effect, forming a complete permission set.
WorkOS supports both single-role and multi-role modes, and group roles are resolved differently in the two modes.
WorkOS User Groups is part of its authorization system, built on top of the existing user directory and role model.
AuthKit has fully translated its hosted pages, emails and Widgets into 90 locales.
WorkOS engineering manager Nick Nisi and applied AI team engineer Zach Proser proposed at the AI Engineer workshop that an agent's "completion" should be turned from the model's self-report into reproducible evidence.
Against the backdrop of frequent security incidents, enterprises should treat identity infrastructure as a core component of the security architecture rather than an auxiliary feature.
WorkOS recommends that teams review dependency lock files, enable package integrity verification, and monitor anomalous outbound network behavior.
40 more timeline events
All Facts (20)
WorkOS is a technology company focused on providing enterprise-grade identity authentication and user management infrastructure for SaaS applications, with products covering core enterprise IT capabilities such as SSO (Single Sign-On), SCIM directory synchronization, and audit logs.
65%UnverifiedWorkOS was originally positioned to help SaaS products quickly integrate enterprise-grade identity capabilities such as SSO and directory sync.
50%UnverifiedWorkOS User Groups is part of its authorization system, built on top of the existing user directory and role model.
50%UnverifiedWorkOS supports both single-role and multi-role modes, and group roles are resolved differently in the two modes.
50%UnverifiedIn multi-role mode, the roles corresponding to the various groups a user belongs to stack and take effect, forming a complete permission set.
50%UnverifiedAuthKit has fully translated its hosted pages, emails and Widgets into 90 locales.
50%UnverifiedWorkOS engineering manager Nick Nisi and applied AI team engineer Zach Proser proposed at the AI Engineer workshop that an agent's "completion" should be turned from the model's self-report into reproducible evidence.
50%UnverifiedAgainst the backdrop of frequent security incidents, enterprises should treat identity infrastructure as a core component of the security architecture rather than an auxiliary feature.
50%UnverifiedWorkOS recommends that teams review dependency lock files, enable package integrity verification, and monitor anomalous outbound network behavior.
50%UnverifiedThis automatic capture is not retroactive; events that occurred before it was enabled will not be backfilled.
50%UnverifiedWorkOS's Directory Sync feature connects to enterprise identity providers (such as Okta, Azure AD and Google Workspace) via the SCIM protocol.
50%UnverifiedAutomatic capture covers only two types of events, sign-in sessions and membership changes; other custom business operations still require developers to actively report them via the Audit Logs API.
50%UnverifiedWorkOS previously did not persistently store sign-in and membership change events for audit purposes, so they cannot be backfilled retroactively.
50%UnverifiedFor products using WorkOS for enterprise-grade SSO and Directory Sync, this update lowers integration costs and is particularly helpful for meeting compliance requirements such as SOC 2 and ISO 27001.
50%UnverifiedMembership change events are generated on the Directory Sync path: group changes on the IdP side are pushed via SCIM, triggering WorkOS to update organization membership, which is then written to the audit log.
50%UnverifiedIf a compliance audit needs to cover a longer historical period, teams should enable this feature as early as possible and check the receiving configuration of downstream logging systems (such as a SIEM).
50%UnverifiedIf an application has its own membership management entry point independent of the IdP, those membership changes will not automatically enter the WorkOS audit log.
50%UnverifiedPreviously, developers had to manually call WorkOS's audit log API to record sign-in and membership change actions.
50%Unverifiedauth.md was proposed by WorkOS and is still in an early adoption stage; it lets services use a Markdown file to describe registration, authentication, and available permissions, supporting two modes: Agent verified and User claimed.
50%UnverifiedWorkOS exposes a standardized provisioning interface through the Provisioning API.
50%