Windmill
Windmill absorbed dbt, un-gated its warehouse languages, and turned AI authoring on by default.
A side-by-side editorial comparison of RSS-Bridge and Resend — release velocity, themes, recent moves, and the top alternatives to consider.
The web's duct-tape RSS layer, now quiet for a year after flipping every bridge on by default.
RSS-Bridge generates feeds for sites that removed theirs, and each release is a batch of community fixes to individual bridges plus a handful of new ones. Releases are date-tagged rather than versioned and land every few months, with the most recent in August 2025 — roughly a year of silence since. The core is stable PHP; the churn is in the ~400 site-specific scrapers that break whenever a target site changes markup or adds bot protection.
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.
RSS-Bridge generates feeds for sites that removed theirs, and each release is a batch of community fixes to individual bridges plus a handful of new ones. Releases are date-tagged rather than versioned and land every few months, with the most recent in August 2025 — roughly a year of silence since. The core is stable PHP; the churn is in the ~400 site-specific scrapers that break whenever a target site changes markup or adds bot protection.
The project has been shifting from a curated tool to a general-purpose scraping surface: bridges are now all enabled by default, caching was rewritten, and token-based URL auth was added to make public instances survivable. That combination points at operators running shared instances rather than individuals running one bridge. The maintenance load, however, is entirely community-carried, and the gap since the last release suggests that pipeline has thinned.
The next release is likely another routine batch of bridge repairs and additions rather than a core change. The stated intentions in these notes — raising the minimum PHP version and separating the document root from the data folder — remain unshipped, and nothing here indicates when that lands.
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.
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.
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.
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 RSS-Bridge or Resend.
Windmill absorbed dbt, un-gated its warehouse languages, and turned AI authoring on by default.
Nine releases in four days, all of them small — Casdoor is grinding on tenant-level governance.
Prowler turned its assistant from a read-only explainer into something that can change your tenant.
NetBox is spending 4.6 paying down query cost, not adding models.
Depot is no longer a build accelerator — it is assembling the whole CI stack underneath itself.
Buildkite is rebuilding its MCP server around what an agent actually does with a failed build.
See all RSS-Bridge alternatives → · See all Resend alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Resend is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Resend is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top RSS-Bridge alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "RSS-Bridge alternatives" section above for the current picks, or visit /alternatives/rss-bridge for the full list with editorial commentary on each.
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.