WorkOS
WorkOS provides APIs and tools that help developers add enterprise features like SSO and directory sync to their applications.
About this data
Updated August 10, 2026
Overall Pulse Score
+5 over this period
A 0-100 index summarizing the tone of 94 relevant public mentions gathered from public online communities across 17 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.
Weekly Sentiment Trend
Pulse Score by week over the selected period. Each point is one complete week of mentions.
This week in public discussion
Recent discussion around WorkOS over the past several weeks has leaned negative, with commenters reporting a notable volume of bugs and reliability concerns. Mentions frequently described redirect URI errors, invalid scope rejections, and unexpected API behavior breaking existing integrations without code changes on the user side. Some praise did surface around specific features and integration quality, but complaint themes around bugs and reliability outweighed positive sentiment by a considerable margin in the tracked period.
Read the deeper analysisAI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.
Sentiment mix by week
How the tone of public discussion splits each week.
Ringed points mark weeks with unusually high discussion volume, more than double this product's typical week.
Most-discussed praise
Most-discussed complaints
Themes across the selected period, with mention counts.
How WorkOS compares
Pulse Score over the selected period versus the top tracked competitors in Coding.
Where the mentions come from
Share of the 94 relevant public mentions in the selected period, by source.
Sample public mentions
Showing 5 of 94 analyzed public mentions in this period, with links to the original source. We do not reproduce full threads.
“Feature request: use PKCE always. OAuth 2.1 specification recommends PKCE even for server <> server. We have the tools now that we're using workos-node@^8, so it's be great if this was setup :)”
“WorkOS invalid_redirect_uri: claim-web-apps registers oauth2-proxy.lab (NXDOMAIN) but oauth2-proxy uses oauth.lab. ## Symptom After the redirect fix (#2510/#2513), dozzle/obsidian correctly 302 to WorkOS, but WorkOS returns error=invalid_redirect_uri and login can't complete. Roo...”
“oauth2-proxy: login redirect not completing — browser shows raw '302 Found' link instead of WorkOS login. ## Symptom After the ForwardAuth netpol fix (#2506/#2507), oauth2-protected routes (dozzle, obsidian) no longer 500 — oauth2-proxy returns 401 for unauthenticated requests. B...”
“challengeFactor() (and any all-optional-body endpoint) sends [] instead of {}, rejected by API with 422. This has only started failing today and no code changes have been made to the SDK. My guess is a changed was made on your APIs to reject this. **Affected versions:** confirmed...”
“Placeholder misalignment in pre-release Firefox. In the latest version of Firefox Developer Edition on macOS (151.0b1), AuthKit's input placeholders are misaligned. This should be fixed in AuthKit and/or a bug reported to Mozilla before this version of Firefox becomes stable to p...”
89+ more analyzed mentions, full history, and theme breakdowns are part of Pro.
Get ProDeeper analysis
- Bug reports and reliability complaints dominated discussion by a wide margin over the four-week window.
- Sentiment spiked briefly in early June then declined steadily, ending the window at a notably lower point than the peak.
- Opinion was divided between commenters who valued the feature set and integration potential and those frustrated by recurring authentication failures.
- Several mentions tied reliability concerns to apparent platform-side changes rather than user code, sharpening the tone of complaint.
| Praise theme | Mentions |
|---|---|
| Strong features | 20 |
| Good integrations | 20 |
| Easy to use | 10 |
| Feature requests | 3 |
| Security praise | 3 |
| Complaint theme | Mentions |
|---|---|
| Bugs | 43 |
| Reliability | 23 |
| Missing features | 19 |
| Lacking integrations | 12 |
| Feature requests | 5 |
Discussion around WorkOS over the four-week window was heavily weighted toward frustration, with complaint themes outnumbering praise themes by a wide margin in raw mention counts. Bug reports alone accounted for the single largest cluster of commentary, and reliability concerns followed closely behind. Commenters described a recurring pattern of authentication flows breaking at multiple points, including redirect URI rejections, invalid scope errors, and SDK endpoints sending malformed request bodies. Several mentions pointed to issues that appeared without any changes on the user side, which sharpened the tone of grievance and fed into reliability concerns as a distinct thread of its own.
The score trajectory over the window tells a story of volatility and gradual erosion. Discussion opened at low single-data-point readings before climbing sharply in early June, suggesting a brief period where positive or neutral commentary dominated. That peak was short-lived, and sentiment slid through mid-June before a modest recovery late in the month. The most recent data point, carrying fewer mentions, pulled back down considerably, suggesting the recovery did not hold and that unresolved issues continued to surface.
Where opinion divided most visibly was between commenters who acknowledged WorkOS as a capable integration target worth building toward and those who found the day-to-day reliability unworkable. Praise themes around features and integration quality were not trivial in count, suggesting a segment of the audience held a genuinely positive view of what the product offers in principle. The tension was less about whether the feature set was desirable and more about whether it could be depended upon in practice.
Sample mentions reinforced the reliability narrative with specificity, citing broken ingress configurations, lazy token refresh behavior causing forced re-logins, and SDK regressions tied to apparent API-side changes. The tone in these mentions was largely technical and diagnostic rather than dismissive, but the cumulative weight of unresolved issues colored the overall discussion negatively.
AI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.
Member perspectives
Individual opinions from Pro members, posted over time. These are personal member views, not aggregated sentiment data.
Overall Pulse Score
+5 over this period
A 0-100 index summarizing the tone of 94 relevant public mentions gathered from public online communities across 17 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.
Data summary
Compare with another tool
WorkOS
40
Trainual
88
Score-level preview from live weekly tracking.
Are you WorkOS?
Get a private enterprise dashboard for your product - full history, every source, theme deep-dives, and weekly alerts. You can also respond to the data shown here.
Explore the enterprise dashboardAffiliate disclosure
Some links on this site may be affiliate links. If you click one and make a purchase, we may earn a commission at no extra cost to you. Learn more.
Is WorkOS your product?
See everything behind this page - full history, every source, theme deep-dives, and weekly alerts - in a private enterprise dashboard.
Request early accessCompare with similar tools
Safari MCP Server
A Model Context Protocol server that gives AI assistants programmatic access to Safari browser automation for developers.
Free
View DetailsRevenueCat
A platform that manages in-app purchases, subscriptions, and revenue analytics for iOS and Android app developers.
Free tier; paid plans available
View Details