Dashy
The self-hosted dashboard finally let you drag things around instead of editing YAML.
Comparison · Infra & APIs
Windmill vs BorgBackup
A side-by-side editorial comparison of Windmill and BorgBackup — release velocity, themes, recent moves, and the top alternatives to consider.
Windmill vs BorgBackup: at a glance
What is Windmill?
Windmill collapsed its deployment model, opened two paid runtimes, and let an agent build the workspace.
Ten days in late July carried three unrelated structural changes. The workspace-level deploy target was removed entirely — a workspace now deploys into its lineage parent, so the setting can no longer disagree with itself, and job tags resolve $workspace against the nearest provisioned ancestor. BigQuery and Snowflake moved out from behind the Enterprise license into community builds. AI sessions entered beta enabled by default, tying a chat to a workspace or fork with a live preview, producing scripts, flows and apps as drafts reviewed in a diff drawer. The surrounding releases are AI chat refinements: file attachments read on demand, web search sources shown with the query.
What is BorgBackup?
Borg's long-running 2.0 beta finally landed packs — and warned it dropped back to alpha quality.
Borg runs two trains in the same feed. The 1.4.x line is explicitly a refreshed 1.2 — same features and behaviour, with the riskier changes isolated so they could be tested before shipping — and it has taken over as the recommended branch since 1.2.9 was called the final 1.2 release. The 2.0 line has been in beta since well before this window, at b22 as of July 2026, with every release carrying a do-not-use-on-production warning. b22 introduced packs and the maintainers told users to expect alpha stability despite the beta number.
Windmill vs BorgBackup: editorial side-by-side
Windmill
8.8INFRA · APIS
Windmill collapsed its deployment model, opened two paid runtimes, and let an agent build the workspace.
◆ Current state
Ten days in late July carried three unrelated structural changes. The workspace-level deploy target was removed entirely — a workspace now deploys into its lineage parent, so the setting can no longer disagree with itself, and job tags resolve $workspace against the nearest provisioned ancestor. BigQuery and Snowflake moved out from behind the Enterprise license into community builds. AI sessions entered beta enabled by default, tying a chat to a workspace or fork with a live preview, producing scripts, flows and apps as drafts reviewed in a diff drawer. The surrounding releases are AI chat refinements: file attachments read on demand, web search sources shown with the query.
◆ Where it's heading
All three moves push in the same direction — making the workspace itself the unit an agent can safely operate on. A single derived deployment target removes the ambiguity an automated change would otherwise have to resolve; the diff drawer and Compare & Deploy give a review gate for machine-authored artifacts; parallel sessions assume more changes in flight than a person would make by hand. Windmill is building the promotion path first and the agent second, which is the opposite order from most tools that added a chat and then discovered they needed review.
◆ Prediction
Expect AI sessions to leave beta with the diff and deploy path as the safety story, and more runtimes to follow BigQuery and Snowflake out of the Enterprise tier — Oracle DB and MS SQL are the two named as still gated. The compressed release timing suggests these landed as one planned batch rather than a new sustained pace.
BorgBackup
6.3INFRA · APIS
Borg's long-running 2.0 beta finally landed packs — and warned it dropped back to alpha quality.
◆ Current state
Borg runs two trains in the same feed. The 1.4.x line is explicitly a refreshed 1.2 — same features and behaviour, with the riskier changes isolated so they could be tested before shipping — and it has taken over as the recommended branch since 1.2.9 was called the final 1.2 release. The 2.0 line has been in beta since well before this window, at b22 as of July 2026, with every release carrying a do-not-use-on-production warning. b22 introduced packs and the maintainers told users to expect alpha stability despite the beta number.
◆ Where it's heading
The split is the story: one branch exists purely to keep existing users safe and current, while the other rewrites how data is stored on disk. Packs are the kind of change that determines whether 2.0 ever ships — repository layout affects performance, resumability and every recovery path at once, and the honesty about stability regressing suggests the shakeout is still ahead. The 1.4 line will keep absorbing fixes and low-severity security work in the meantime, and the b18 corruption bug shows why the two trains are kept firmly apart.
◆ Prediction
Expect further 2.0 betas focused on packs stability before anything resembling a release candidate, with 1.4.x continuing to carry routine fixes for production users.
Alternatives to Windmill and BorgBackup
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 BorgBackup.
RSS-Bridge
The web's duct-tape RSS layer, now quiet for a year after flipping every bridge on by default.
Jackett
A daily-shipping indexer proxy whose entire product is a scraper definition file that never stops rotting.
Sonarr
Sonarr's release feed is a two-month run of one-line fixes, most of them about qBittorrent auth.
k0s
k0s ships one fix four times a day — the cost of keeping four Kubernetes branches current.
Microcks
Microcks is quietly wiring LLM example generation into an API mocking tool built for Kubernetes.
See all Windmill alternatives → · See all BorgBackup alternatives →
Recent activity from Windmill and BorgBackup
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4d agoBorgBackup1.4.5: fixes, a low-severity security fix and small features
- 5d agoWindmillOne deployment target, derived from the workspace lineage ⚡
- 5d agoWindmillCompare & Deploy into any workspace
- 10d agoWindmillBigQuery and Snowflake available in the community edition ⚡
- 13d agoBorgBackup2.0.0b22 introduces packs — and warns stability regressed to alpha ⚡
- 13d agoWindmillAI sessions (beta) ⚡
- 14d agoWindmillAttach text files to AI chat messages
- 15d agoWindmillWeb search sources in AI chat
- 4mo agoBorgBackup1.4.4 maintenance release
- 4mo agoBorgBackup2.0.0b21 beta, testing only
- 7mo agoBorgBackup2.0.0b20 beta, testing only
- 8mo agoBorgBackup1.4.3 maintenance release
Frequently asked questions
What is the difference between Windmill and BorgBackup?
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 BorgBackup?
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 BorgBackup?
Top BorgBackup alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "BorgBackup alternatives" section above for the current picks, or visit /alternatives/borgbackup for the full list with editorial commentary on each.