Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Comparison · Infra & APIs
Knock vs Windmill
A side-by-side editorial comparison of Knock and Windmill — release velocity, themes, recent moves, and the top alternatives to consider.
Knock vs Windmill: at a glance
| Feature | Knock | Windmill |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 8.8 |
| Sparks · 30d | 1 | 1 |
| Top themes | notifications, developer-infrastructure, rbac, workflow-automation | workflow orchestration, dbt, open core, ai sessions |
| Last editorial update | 13h ago | 1d ago |
| Website | — | Visit → |
What is Knock?
Knock is hardening for enterprise buyers while its agent takes over the analysis work.
Knock ships weekly, in small, legible increments across three lanes: account governance (custom roles, passkeys), workflow primitives (wait-for-event, branch rebasing), and data ingress (Amplitude, Clay). The newest entry adds granular custom roles, which closes the last obvious gap in account-level access control. Alongside that, the in-product agent gained analytics, letting teams interrogate delivery performance without building reports.
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.
Knock vs Windmill: editorial side-by-side
Knock
6.3INFRA · APIS
Knock is hardening for enterprise buyers while its agent takes over the analysis work.
◆ Current state
Knock ships weekly, in small, legible increments across three lanes: account governance (custom roles, passkeys), workflow primitives (wait-for-event, branch rebasing), and data ingress (Amplitude, Clay). The newest entry adds granular custom roles, which closes the last obvious gap in account-level access control. Alongside that, the in-product agent gained analytics, letting teams interrogate delivery performance without building reports.
◆ Where it's heading
Two arcs run in parallel. The infrastructure lane is buying enterprise credibility — roles, passkeys, audit-grade permissions — the checklist items that decide procurement rather than daily use. The data lane keeps widening what can trigger a workflow: product analytics from Amplitude, enriched rows from Clay, internal Slack channels as a destination. Together they push Knock from a notification API toward the messaging control plane, with the agent as the layer that explains what the plane did.
◆ Prediction
Expect the roles work to continue into audit logs or scoped API keys, since granular permissions without an activity trail is an incomplete enterprise story. More data sources are likely on the same cadence, with the CRM and warehouse categories the obvious remaining gaps.
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.
Alternatives to Knock and Windmill
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 Knock or Windmill.
DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
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
See all Knock alternatives → · See all Windmill alternatives →
Recent activity from Knock and Windmill
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoKnockCustom roles and permissions
- 5d agoWindmillPlan mode for AI sessions
- 6d agoKnockPower internal Slack alerts
- 7d agoKnockCategory + tag management
- 8d agoWindmillNested filter groups and dotted paths in trigger filters
- 9d agoWindmillVersion history for AI session artifacts
- 13d agoKnockAmplitude data source
- 18d agoWindmillRun dbt projects as a first-class Windmill runtime ⚡
- 20d agoKnockAnalytics in the Knock agent ⚡
- 20d agoWindmillOne deployment target, derived from the workspace lineage
- 20d agoWindmillCompare & Deploy into any workspace
- 21d agoKnockWait for event function
Frequently asked questions
What is the difference between Knock and Windmill?
They serve adjacent needs but don't currently overlap on shipped themes. Windmill is currently shipping more aggressively (velocity 8.8 vs 6.3), with 1 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Knock better than Windmill?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Windmill is currently shipping more aggressively (velocity 8.8 vs 6.3), with 1 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Knock?
Top Knock alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Knock alternatives" section above for the current picks, or visit /alternatives/knock for the full list with editorial commentary on each.
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.