Casdoor
Nine releases in four days, all of them small — Casdoor is grinding on tenant-level governance.
Comparison · Infra & APIs
Windmill vs Resend
A side-by-side editorial comparison of Windmill and Resend — release velocity, themes, recent moves, and the top alternatives to consider.
Windmill vs Resend: at a glance
What is Windmill?
Windmill absorbed dbt, un-gated its warehouse languages, and turned AI authoring on by default.
Windmill had a dense fortnight across three fronts. Unmodified dbt projects now run as first-class Windmill scripts — drop the project into a __dbt/ folder, push, and Windmill runs dbt build on your own workers with per-model progress and results, dbt retry and row previews. BigQuery and Snowflake script languages left the Enterprise license and became available on every edition including self-hosted community instances. AI sessions entered beta enabled by default, tying a chat to a workspace or fork with a live preview, building scripts, flows and apps as drafts reviewed in a diff drawer. Deployment also got tightened: Compare & Deploy accepts any target workspace, while the workspace-level 'deploy to' setting was removed in favor of a target derived from workspace lineage.
What is Resend?
Resend spent a month making itself something agents and third-party apps can log into.
Resend is shipping weekly, and the last six weeks split cleanly into two tracks. One is dashboard housekeeping for teams sending at volume: template folders, suppression management from both the dashboard and the API, Message-ID on webhooks and email endpoints for threading. The other is access: a hosted MCP server with OAuth built in, a one-click Claude connector, a Codex marketplace plugin bundling the MCP server and Resend's own skills, and OAuth 2.1 with PKCE so outside developers can build authenticated Resend experiences.
Windmill vs Resend: editorial side-by-side
Windmill
8.8INFRA · APIS
Windmill absorbed dbt, un-gated its warehouse languages, and turned AI authoring on by default.
◆ Current state
Windmill had a dense fortnight across three fronts. Unmodified dbt projects now run as first-class Windmill scripts — drop the project into a __dbt/ folder, push, and Windmill runs dbt build on your own workers with per-model progress and results, dbt retry and row previews. BigQuery and Snowflake script languages left the Enterprise license and became available on every edition including self-hosted community instances. AI sessions entered beta enabled by default, tying a chat to a workspace or fork with a live preview, building scripts, flows and apps as drafts reviewed in a diff drawer. Deployment also got tightened: Compare & Deploy accepts any target workspace, while the workspace-level 'deploy to' setting was removed in favor of a target derived from workspace lineage.
◆ Where it's heading
Windmill is widening what it can be the execution layer for while lowering the price of entry to find out. Running dbt unmodified means a data team can move orchestration without rewriting models, and un-gating the two warehouse languages removes the license wall from exactly the workloads that would arrive alongside dbt. The AI work runs on a distinct principle — output lands as reviewable drafts inside the existing deployment flow rather than as direct changes — which is consistent with the deployment cleanups happening at the same time. One deployment target derived from lineage is the same instinct as one diff drawer before deploy: fewer places where state can disagree.
◆ Prediction
The dbt integration is new enough that scheduling and observability around dbt runs are the obvious next surface, given Windmill already ships per-model results and retry. Expect AI sessions to exit beta on the strength of the draft-and-diff review model rather than by loosening it.
Resend
6.3INFRA · APIS
Resend spent a month making itself something agents and third-party apps can log into.
◆ Current state
Resend is shipping weekly, and the last six weeks split cleanly into two tracks. One is dashboard housekeeping for teams sending at volume: template folders, suppression management from both the dashboard and the API, Message-ID on webhooks and email endpoints for threading. The other is access: a hosted MCP server with OAuth built in, a one-click Claude connector, a Codex marketplace plugin bundling the MCP server and Resend's own skills, and OAuth 2.1 with PKCE so outside developers can build authenticated Resend experiences.
◆ Where it's heading
The second track is the one that changes what Resend is. Shipping an OAuth provider alongside agent-facing distribution turns an API you hold a key for into a platform other software signs into on a user's behalf — the MCP server, the Claude connector and the Codex plugin are all downstream of that auth work. The GitHub secret scanner, which detects and auto-revokes exposed keys, reads as the other half of the same shift: if keys are going to be handled by agents and third-party apps, leaked-key cleanup has to be automatic.
◆ Prediction
Expect the agent surfaces to deepen rather than multiply — scoped OAuth permissions and per-app access controls are the natural follow-on once third parties are authenticating into accounts. More marketplace listings are cheap by comparison and likely to continue alongside.
Alternatives to Windmill and Resend
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 Resend.
Prowler
Prowler turned its assistant from a read-only explainer into something that can change your tenant.
NetBox
NetBox is spending 4.6 paying down query cost, not adding models.
Depot
Depot is no longer a build accelerator — it is assembling the whole CI stack underneath itself.
Buildkite
Buildkite is rebuilding its MCP server around what an agent actually does with a failed build.
Dashy
The self-hosted dashboard finally let you drag things around instead of editing YAML.
See all Windmill alternatives → · See all Resend alternatives →
Recent activity from Windmill and Resend
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoResendTemplate Folders
- 3d agoWindmillRun dbt projects as a first-class Windmill runtime ⚡
- 5d agoWindmillCompare & Deploy into any workspace
- 5d agoWindmillOne deployment target, derived from the workspace lineage
- 7d agoResendEmail Suppressions
- 10d agoWindmillBigQuery and Snowflake available in the community edition ⚡
- 13d agoWindmillAI sessions (beta) ⚡
- 13d agoResendResend Plugin for Codex
- 14d agoWindmillAttach text files to AI chat messages
- 19d agoResendGitHub Secret Scanner
- 22d agoResendOAuth Support ⚡
- 24d agoResendResend Connector for Claude
Frequently asked questions
What is the difference between Windmill and Resend?
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 3 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 Windmill better than Resend?
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 3 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 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 Resend?
Top Resend alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Resend alternatives" section above for the current picks, or visit /alternatives/resend for the full list with editorial commentary on each.