ToolJet
ToolJet runs two release trains at once, and neither has changed direction in months
A side-by-side editorial comparison of Lovable and werf — release velocity, themes, recent moves, and the top alternatives to consider.
Lovable is making generated apps connector-rich and enterprise-shippable at the same time.
Two tracks run in parallel. Generated apps keep gaining third-party reach — payments, file generation and data analysis, and a connector catalogue spanning Twitch, Twilio, Linear, Telegram, Contentful, Calendly, ElevenLabs, Perplexity and Firecrawl, with voice interfaces built on top of the last of those. The second track is governance: a workspace usage dashboard, audit logs filterable by restricted project, Okta SSO and SCIM from the Okta catalogue, external-collaborator restrictions that do not require enforcing SSO on everyone, and Aikido penetration testing on every plan.
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.
Two tracks run in parallel. Generated apps keep gaining third-party reach — payments, file generation and data analysis, and a connector catalogue spanning Twitch, Twilio, Linear, Telegram, Contentful, Calendly, ElevenLabs, Perplexity and Firecrawl, with voice interfaces built on top of the last of those. The second track is governance: a workspace usage dashboard, audit logs filterable by restricted project, Okta SSO and SCIM from the Okta catalogue, external-collaborator restrictions that do not require enforcing SSO on everyone, and Aikido penetration testing on every plan.
Lovable is answering the standing objection to AI app builders — that the output is a prototype — from both ends: giving apps real integrations so they do useful work, and giving the workspaces holding them the controls a security review asks for. Pricing rests on credits rather than seats, and recent work folds every credit type into one balance and makes usage answerable in chat. A runtime panel exposing each AI call an app makes, and TanStack Start as the default framework for Enterprise apps, point the same direction: this output is being treated as production software.
Expect the connector catalogue to keep widening and the enterprise controls to reach deployment itself — approval gates or environment separation are the obvious gaps now that audit logs, SSO and provisioning are in place.
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.
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.
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.
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 Lovable or werf.
ToolJet runs two release trains at once, and neither has changed direction in months
Honeycomb bets that the agent, not the engineer, should notice the anomaly first
Jenkins is shrinking its own war file and rebuilding its UI, one weekly release at a time
Copilot's model roster churns weekly while GitHub quietly rewires policy and billing plumbing
Nexus does the diagnosis; the rest is on-call plumbing
1.38.4 is a security release in all but name, closing ACL gaps across the API.
See all Lovable alternatives → · See all werf alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. werf is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. werf is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Lovable alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Lovable alternatives" section above for the current picks, or visit /alternatives/lovable for the full list with editorial commentary on each.
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.