q2
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
A side-by-side editorial comparison of carrier and Windmill — release velocity, themes, recent moves, and the top alternatives to consider.
carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.
carrier packages an R function together with the data it needs so it can be shipped to another process or machine. 0.3.0 changed the semantics of functions passed through ...: they are now re-crated inside the main crate environment instead of inheriting from wherever they were defined. That fixes helper functions failing to resolve each other remotely, and stops local environments dragging large objects into the payload.
Windmill is dismantling the paywall between itself and the data stack
Three of the last six releases are directional: dbt projects running unmodified as a first-class runtime, BigQuery and Snowflake dropping out of the Enterprise tier, and AI sessions enabled by default in beta. Around them sits careful platform work — workspace lineage as the single deployment target, arbitrary-target Compare & Deploy, schema contracts for DuckLake consumers, and in-app git-to-Windmill sync. Entries are written with migration notes and upgrade paths, which is the tone of a product being run by people who expect it in production.
carrier packages an R function together with the data it needs so it can be shipped to another process or machine. 0.3.0 changed the semantics of functions passed through ...: they are now re-crated inside the main crate environment instead of inheriting from wherever they were defined. That fixes helper functions failing to resolve each other remotely, and stops local environments dragging large objects into the payload.
Each release tightens the boundary between a crate and its surroundings. 0.2.0 introduced .parent_env defaulting to baseenv() to cut the crate off from the global search path and made unnamed ... arguments an error instead of a silent drop; 0.3.0 finishes the job by controlling the environment chain of the packed closures themselves. The package is trading backwards compatibility for predictable, self-contained payloads — a reasonable bet for something whose failures otherwise surface on a remote worker.
The 0.1.0 notes promised an automatic dependency-detection mode to replace explicit packing; nothing since has delivered it, and with the environment semantics now settled that is the obvious next move — though the entries give no date for it.
Three of the last six releases are directional: dbt projects running unmodified as a first-class runtime, BigQuery and Snowflake dropping out of the Enterprise tier, and AI sessions enabled by default in beta. Around them sits careful platform work — workspace lineage as the single deployment target, arbitrary-target Compare & Deploy, schema contracts for DuckLake consumers, and in-app git-to-Windmill sync. Entries are written with migration notes and upgrade paths, which is the tone of a product being run by people who expect it in production.
The company is aiming squarely at data teams and removing every obstacle between them and a self-hosted trial: bring the dbt project as-is, query the warehouse on the community edition, and let the AI build scripts and flows behind the existing draft-and-diff review gate. The governance work advances at the same pace, so the free surface widens without the deployment story loosening. Enterprise is being narrowed to Oracle, MS SQL, and scale rather than to the workloads data teams actually run.
With dbt lineage and DuckLake schema contracts both landed, the likely next step is unifying them — a single asset graph spanning dbt models and materialized tables, with contract validation running across the boundary.
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 carrier or Windmill.
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
The metadata cache under pak now speaks to authenticated and corporate repositories.
R's old dependency manager now runs on a vendored copy of its own successor.
A fake web server for tests that keeps closing the gap with the real thing.
Hit 1.0, relicensed to MIT, and has shipped almost nothing but dbplyr compatibility since.
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
See all carrier alternatives → · See all Windmill alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Windmill is currently shipping more aggressively (velocity 8.8 vs 0.0), with 3 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. Windmill is currently shipping more aggressively (velocity 8.8 vs 0.0), with 3 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 carrier alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "carrier alternatives" section above for the current picks, or visit /alternatives/carrier for the full list with editorial commentary on each.
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.