Customer identity (CIAM)
What is WorkOS? An introduction to the API platform for enterprise features
WorkOS is a set of developer APIs and SDKs for adding enterprise features such as Single Sign-On, Directory Sync and Audit Logging to an app. It describes itself as an API platform for User Management, SSO (SAML), Directory Sync (SCIM) and the Admin Portal. It is aimed at developers and at SaaS companies becoming enterprise ready.
- Tool
- WorkOS
- Made by
- WorkOS
- Official site
- workos.com
- Category
- Customer identity (CIAM)
Who makes WorkOS
WorkOS is developed by WorkOS, the company that shares its name with the product. The vendor's official website is linked below this introduction, and it is the place to confirm current product details.
Official website: workos.com
What WorkOS is for
WorkOS exists so that an application team does not have to build each enterprise identity feature from scratch. It provides developer APIs and SDKs for features such as Single Sign-On, Directory Sync and Audit Logging, which are the capabilities larger organizations commonly expect from the software they adopt.
The stated aim is to let developers add enterprise features such as SSO in minutes using only a few lines of code. A single integration supports any SAML or OIDC identity provider, so an app does not need a separate build for each customer's identity system. WorkOS also says one integration point covers more than 20 enterprise services.
Who WorkOS is for
The vendor names three audiences: developers, SaaS companies that are becoming enterprise ready, and IT administrators. Developers work with the APIs and SDKs directly. SaaS companies use the platform to meet the identity expectations of larger customers.
IT administrators reach WorkOS through the Admin Portal, a hosted interface that lets them set up WorkOS themselves. This means the customer's own administrators can configure their side of an integration without relying on the app's developers.
Notable capabilities
WorkOS combines enterprise connection features with general user authentication, and exposes them through a consistent developer interface. The capabilities below come from the vendor's own description.
- Single Sign-On through one integration that supports any SAML or OIDC identity provider.
- Directory Sync, which enables user lifecycle management by syncing the app with enterprise employee directory systems. Directory services can push realtime updates through webhook events.
- Audit Logging as one of the core enterprise features offered through the APIs.
- User and organization management with policies and support for all auth types, including sign-in with social providers such as Microsoft and Google.
- Passwordless authentication through a six-digit code sent by email.
- A hosted Admin Portal that IT admins use to set up WorkOS themselves, and that can be branded to match the customer's app.
- A RESTful API that returns JSON with normalized objects, plus official SDKs for several languages, including Node.js, Ruby, Python, .NET and Go.
- Support for multiple environments to match an app's development process.
How WorkOS fits customer identity (CIAM)
Customer identity, often shortened to CIAM, covers how the people who use an application sign up, sign in and are managed. WorkOS sits in this category as a developer-focused platform: it supplies user management and authentication types alongside the enterprise connection features that business customers tend to request.
Within Lockhelm's wider niche of password managers, SSO, identity, MFA and access control, WorkOS is most relevant to SSO and directory-based access. Its SAML and OIDC support addresses sign-on, while Directory Sync and SCIM address how user accounts are created and updated from an employer's directory. Audit Logging relates to the record-keeping side of access control.
WorkOS can also sign HIPAA business associate agreements for eligible customers, which may matter to teams handling health-related data. As with any identity component, teams should review the vendor's documentation against their own requirements.
Frequently asked questions
What is WorkOS used for?
WorkOS is used to add enterprise features such as Single Sign-On, Directory Sync and Audit Logging to an app through developer APIs and SDKs. It also includes user and organization management.
Who develops WorkOS?
WorkOS is developed by WorkOS. The vendor's official website is at https://workos.com.
Does WorkOS support SAML and OIDC?
Yes. A single WorkOS integration supports any SAML or OIDC identity provider.
Which programming languages does WorkOS support?
Official SDKs are available for several languages, including Node.js, Ruby, Python, .NET and Go. The API is RESTful and returns JSON with normalized objects.
Can IT administrators configure WorkOS themselves?
Yes. The Admin Portal is a hosted interface that lets IT admins set up WorkOS themselves, and it can be branded to match the customer's app.
Lockhelm is independent and is not affiliated with WorkOS. Product names belong to their owners. Features change; confirm details on the official website.