WorkOS
@WorkOS
Followers
7,353
Following
4
Media
238
Statuses
968
The modern platform for auth & user identity. 🚀 Check out @AuthKit ✨ @Radix_ui 🎨 and @Warrant_dev ⚙️
Joined January 2020
Don't wanna be here?
Send us removal request.
Explore trending content on Musk Viewer
Linkin Park
• 180942 Tweets
Adalet
• 180261 Tweets
Gazze
• 115749 Tweets
Chester
• 94159 Tweets
ベイマックス
• 94026 Tweets
小泉進次郎
• 86384 Tweets
#INZM_HyperBandLive
• 45079 Tweets
#笑うマトリョーシカ
• 41100 Tweets
知的レベル
• 40845 Tweets
雇用統計
• 36293 Tweets
資さんうどん
• 35938 Tweets
大阪府警
• 33800 Tweets
エイリアン
• 33059 Tweets
Game Day
• 22514 Tweets
#ساعه_استجابه
• 22209 Tweets
神ちゃん
• 19289 Tweets
#Aスタプラス
• 15707 Tweets
NANON LETSGO NYFW
• 14035 Tweets
KIDNAP CHAPTER ONE
• 13197 Tweets
ビーズリー
• 11064 Tweets
ロムルス
• 10958 Tweets
シングルス
• 10361 Tweets
August Updates
► SAML certificate renewal flow
► Organization switching APIs
► Modeling your app docs
► Provider icons API
0
0
0
You can now retrieve provider icons for IdPs, Directory Sync, and domain verification services used within the Admin Portal. They can be accessed through a new endpoint or downloaded as Figma files.
0
0
5
Renewing SAML certificates is now easier than ever 🚀
► Send renewal flows directly to admins via the Admin Portal
► Receive alerts for connections approaching their expiration date
► Filter orgs based on time remaining until expiration
0
0
1
Delayed time to market is one of the biggest drawbacks of building SSO and SCIM in-house.
Over three years, this can lead to a potential revenue loss of $7.95M with an ROI of just 9%, compared to 1,954% when using WorkOS.
0
0
2
For AI startups like
@heyjasperai
,
@perplexity_ai
, and
@cursor_ai
, modularity, ease of integration, and the level of technical support are some of the reasons for choosing WorkOS.
Proactively drive enterprise growth for your AI app with WorkOS:
0
0
1
Documentation covering common auth scenarios and concepts like B2B app modeling and multi-tenancy is now available.
See how WorkOS can fit into your existing architecture as you model the integration.
0
1
4
Building SSO & SCIM from scratch requires ongoing engineering investment to scale — supporting more IdPs, managing expiring SAML certificates, and standardizing onboarding fragmentation.
And this is separate from the initial 3-6 month development cycle.
0
0
1
User deprovisioning is a key use case for SCIM, automatically updating access to apps and resources when employment status changes in the IdP.
SCIM also supports:
► Pre-provisioning
► User onboarding emails
► Automated access management
0
0
1
🚀 July Updates 💫
► RBAC for AuthKit
► Fine-Grained Authorization early access
► SCIM role assignment
► new Log Streams destination
► updated Node SDK
0
0
2
With a ton of user growth and enterprise traction,
@warpdotdev
needed a reliable SSO solution that could easily plug into their existing auth setup.
With WorkOS, Jeff's team was able to ship SSO in less than a day, requiring minimal maintenance since.
0
0
3
Early access for Fine-Grained Authorization (FGA) is now available.
FGA is a more granular form of access control that allows apps to grant users certain behaviors per resource. It's the most scalable & foolproof way to handle AuthZ for enterprises.
1
1
4
.
@PlanetScale
chose WorkOS because they needed an all-in-one solution for both SSO and SCIM provisioning.
They shipped enterprise features in days instead of months, avoiding SSO maintenance that can require "teams of up to seven engineers."
0
2
11
Most AuthZ solutions require your customer’s admin to create the data source for roles, resources, and permissions inside your app.
With identity provider-based authorization systems via SCIM, the admin can use data that already exists in their IdP.
0
0
7
Building authorization in-house is progressive, evolving from basic admin roles, n>2 roles (RBAC), and ultimately resource-based authorization (FGA).
Our latest Developer's Guide includes practical guidance for engineers implementing these systems.
0
0
2
What's the key to DevRel for AI products?
🧵 3 important takeaways from Crossing the Enterprise Chasm with
@beardigsit
, who leads developer relations at
@pinecone
.
1) Where DevRel lives in the org chart: If within product teams, DevRel is launching feature previews and ensuring
0
0
3