ToolJet
ToolJet runs two release trains at once, and neither has changed direction in months
Comparison · Infra & APIs
Merge vs werf
A side-by-side editorial comparison of Merge and werf — release velocity, themes, recent moves, and the top alternatives to consider.
Merge vs werf: at a glance
| Feature | Merge | werf |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | unified-api, integrations, sync-reliability, accounting | multi-channel-releases, buildah, concurrency-fixes, kubernetes-deploy |
| Last editorial update | 7d ago | 5h ago |
| Website | — | Visit → |
What is Merge?
Merge's weekly cadence is all connector depth: no new categories, no agent surface.
Merge ships a dated digest every week, and for the last three months the contents have been uniform: per-connector mapping fixes, pagination and sync-reliability work, and incremental field coverage across Sage Intacct, NetSuite, SharePoint and QuickBooks Online. The one product-surface change in the window is per-integration customization of the Link setup flow, which lets customers hide auth steps and the Selective Sync screen for specific integrations. Everything else is fidelity work on integrations Merge already supports.
What is werf?
Four channels, one fix stream — werf's releases are mostly concurrency repairs.
werf publishes the same work across alpha, beta, ea, and stable channels plus a 3.x dev line, so a single fix surfaces three or four times under different version numbers. The substance in this window is almost entirely build-engine concurrency: parallel recovery failures, races in Dockerfile builds, concurrent stderr access, serialized base image pulls, retries when a cached image id goes missing. New function is thin — a case-insensitive-condition-tracking feature gate, a build time summary in debug mode, and a registry-side cleanup report.
Merge vs werf: editorial side-by-side
Merge
5.0INFRA · APIS
Merge's weekly cadence is all connector depth: no new categories, no agent surface.
◆ Current state
Merge ships a dated digest every week, and for the last three months the contents have been uniform: per-connector mapping fixes, pagination and sync-reliability work, and incremental field coverage across Sage Intacct, NetSuite, SharePoint and QuickBooks Online. The one product-surface change in the window is per-integration customization of the Link setup flow, which lets customers hide auth steps and the Selective Sync screen for specific integrations. Everything else is fidelity work on integrations Merge already supports.
◆ Where it's heading
The arc points at depth over breadth. Merge is spending its release budget making existing connectors survive large accounts — big item catalogs, user-defined dimensions, high attachment volumes — rather than adding new verticals. Accounting and File Storage absorb most of each week's entries, with ATS and CRM getting steady but thinner attention, and nothing in the window suggests a change to the unified-API model itself.
◆ Prediction
Expect the next several digests to continue the Sage Intacct, NetSuite and SharePoint deepening, with further Link-flow configuration options as the main user-visible additions. The entries give no signal either way on whether Merge plans an agent- or MCP-facing surface.
werf
5.0INFRA · APIS
Four channels, one fix stream — werf's releases are mostly concurrency repairs.
◆ Current state
werf publishes the same work across alpha, beta, ea, and stable channels plus a 3.x dev line, so a single fix surfaces three or four times under different version numbers. The substance in this window is almost entirely build-engine concurrency: parallel recovery failures, races in Dockerfile builds, concurrent stderr access, serialized base image pulls, retries when a cached image id goes missing. New function is thin — a case-insensitive-condition-tracking feature gate, a build time summary in debug mode, and a registry-side cleanup report.
◆ Where it's heading
The 3.x dev line is accumulating what 2.x is stabilizing, and the one genuinely new thing in it is a deno binary embedded into werf releases behind a build tag. That is the only entry pointing anywhere beyond maintenance, and it is gated, so its intent is not yet stated. Otherwise the pattern is a mature build tool hardening buildah paths under parallelism, which is where self-hosted CI hits it hardest.
◆ Prediction
The embedded deno work is the thread to watch — if it stays behind its build tag it is an experiment, and if 3.x ships it on by default it implies a scripting surface for deployment.
Alternatives to Merge and werf
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 Merge or werf.
Honeycomb
Honeycomb bets that the agent, not the engineer, should notice the anomaly first
Jenkins
Jenkins is shrinking its own war file and rebuilding its UI, one weekly release at a time
GitHub
Copilot's model roster churns weekly while GitHub quietly rewires policy and billing plumbing
incident.io
Nexus does the diagnosis; the rest is on-call plumbing
ZoneMinder
1.38.4 is a security release in all but name, closing ACL gaps across the API.
Recent activity from Merge and werf
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 16h agowerf2.77.1 fixes buildah imports on symlinked paths
- 16h agowerf3.x dev embeds deno and adds a registry-side cleanup report
- 1d agowerf2.76.0 adds condition-tracking gate and build timing
- 5d agowerflatest-signature
- 5d agowerf2.75.3 stops host cleanup wiping other versions' git cache
- 5d agowerf2.75.4 serializes base image pulls and fixes stapel scripts
- 12d agoMergeQuickBooks webhook format support, NetSuite and Sage speedups
- 19d agoMergeLink setup flow becomes configurable per integration
- 26d agoMergeSync error and pagination fixes across Greenhouse, Lever, SharePoint
- 1mo agoMergeXero attachments accept Base64 uploads; NetSuite filter fix
- 1mo agoMergeNew employee and expense filters; NetSuite single-subsidiary writes
- 1mo agoMergeDirect Xero attachment uploads; Teams sensitivity labels
Frequently asked questions
What is the difference between Merge and werf?
They serve adjacent needs but don't currently overlap on shipped themes. Merge and werf are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Merge better than werf?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Merge and werf are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Merge?
Top Merge alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Merge alternatives" section above for the current picks, or visit /alternatives/merge-dev for the full list with editorial commentary on each.
What are the best alternatives to werf?
Top werf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "werf alternatives" section above for the current picks, or visit /alternatives/werf for the full list with editorial commentary on each.