DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Comparison · Infra & APIs
Windmill vs WorkOS
A side-by-side editorial comparison of Windmill and WorkOS — release velocity, themes, recent moves, and the top alternatives to consider.
Windmill vs WorkOS: at a glance
| Feature | Windmill | WorkOS |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 8.8 | 8.8 |
| Sparks · 30d | 1 | 2 |
| Top themes | workflow orchestration, dbt, open core, ai sessions | identity, authentication, ai-agents, scim |
| Last editorial update | 1d ago | 12h ago |
| Website | Visit → | — |
What is Windmill?
Windmill gave away the warehouse connectors and now runs dbt natively — the trial is the strategy.
Two lines are moving at once. The platform line made dbt projects a first-class runtime, unified the deployment target on workspace lineage, opened Compare & Deploy to arbitrary target workspaces, and moved BigQuery and Snowflake out from behind the Enterprise license. The AI line took sessions to beta on by default and has been adding controls around them since — file attachments, visible web-search sources, artifact version history, and now a read-only plan mode that refuses anything that writes or deploys until you approve a plan.
What is WorkOS?
WorkOS is building identity for agents while quietly fixing the sign-up funnel.
WorkOS ships several small entries a week, and August splits cleanly in two. One half is authentication housekeeping for human users: an Android SDK, deliverability checks that reject undeliverable addresses at sign-up, invitation acceptance counting as email verification, and a reversible SCIM proxy for migrating directory connections without downtime. The other half is agent infrastructure — Agent Registration via the auth.md protocol, and the Pipes Token Proxy that calls third-party APIs on a user's behalf without the application ever touching their token.
Windmill vs WorkOS: editorial side-by-side
Windmill
8.8INFRA · APIS
Windmill gave away the warehouse connectors and now runs dbt natively — the trial is the strategy.
◆ Current state
Two lines are moving at once. The platform line made dbt projects a first-class runtime, unified the deployment target on workspace lineage, opened Compare & Deploy to arbitrary target workspaces, and moved BigQuery and Snowflake out from behind the Enterprise license. The AI line took sessions to beta on by default and has been adding controls around them since — file attachments, visible web-search sources, artifact version history, and now a read-only plan mode that refuses anything that writes or deploys until you approve a plan.
◆ Where it's heading
Windmill is positioning as the place a data team's existing work already runs rather than a system to be ported to: an unmodified dbt project drops in, its models become addressable assets with ref() lineage, and the warehouse languages needed to reach them are no longer paywalled. In parallel, the AI session work is maturing from capability to governance — the recent additions are all about reviewability and constraint, not raw autonomy. The deployment changes point the same way, collapsing configurable targets into a single derived answer.
◆ Prediction
Expect the plan-and-approve posture to spread beyond session chats into the durable AI surfaces, and more warehouse-adjacent runtimes to follow dbt into the first-class treatment; Oracle and MS SQL remain the obvious Enterprise holdouts to watch.
WorkOS
8.8INFRA · APIS
WorkOS is building identity for agents while quietly fixing the sign-up funnel.
◆ Current state
WorkOS ships several small entries a week, and August splits cleanly in two. One half is authentication housekeeping for human users: an Android SDK, deliverability checks that reject undeliverable addresses at sign-up, invitation acceptance counting as email verification, and a reversible SCIM proxy for migrating directory connections without downtime. The other half is agent infrastructure — Agent Registration via the auth.md protocol, and the Pipes Token Proxy that calls third-party APIs on a user's behalf without the application ever touching their token.
◆ Where it's heading
The agent work is the strategic line. Registration gives an agent an identity of its own instead of a borrowed human session; the token proxy means an application acting for a user never holds the credential. Together they describe a stack where an agent can be authorized, audited and revoked as a first-class principal. The human-auth releases are conversion and migration work — the deliverability check and SCIM Bridge both remove reasons a customer stalls — which is what a developer-infrastructure company does while its next category is still forming.
◆ Prediction
Registration and the token proxy leave scoping and revocation as the visible gaps, so expect per-agent permissions or consent surfaces next. Whether auth.md gains adoption beyond WorkOS is not something these entries can answer.
Alternatives to Windmill and WorkOS
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Windmill or WorkOS.
Casdoor
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
NetBox
NetBox adds a cooling data model — the first new infrastructure domain since power
See all Windmill alternatives → · See all WorkOS alternatives →
Recent activity from Windmill and WorkOS
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoWorkOSAndroid SDK
- 2d agoWorkOSHigher quality sign-ups with email deliverability checks
- 5d agoWindmillPlan mode for AI sessions
- 5d agoWorkOSMigrate SCIM Connections with SCIM Bridge
- 6d agoWorkOSAccepted invitations count as email verification
- 8d agoWindmillNested filter groups and dotted paths in trigger filters
- 9d agoWindmillVersion history for AI session artifacts
- 13d agoWorkOSPipes Token Proxy ⚡
- 15d agoWorkOSAgent Registration ⚡
- 18d agoWindmillRun dbt projects as a first-class Windmill runtime ⚡
- 20d agoWindmillOne deployment target, derived from the workspace lineage
- 20d agoWindmillCompare & Deploy into any workspace
Frequently asked questions
What is the difference between Windmill and WorkOS?
They serve adjacent needs but don't currently overlap on shipped themes. Windmill and WorkOS are shipping at a similar cadence (velocity 8.8 vs 8.8, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Windmill better than WorkOS?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Windmill and WorkOS are shipping at a similar cadence (velocity 8.8 vs 8.8, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Windmill?
Top Windmill alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Windmill alternatives" section above for the current picks, or visit /alternatives/windmill for the full list with editorial commentary on each.
What are the best alternatives to WorkOS?
Top WorkOS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "WorkOS alternatives" section above for the current picks, or visit /alternatives/workos for the full list with editorial commentary on each.