authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Comparison · Infra & APIs
MainWP vs werf
A side-by-side editorial comparison of MainWP and werf — release velocity, themes, recent moves, and the top alternatives to consider.
MainWP vs werf: at a glance
What is MainWP?
MainWP's pulse is a steady drip of per-extension maintenance, not headline features.
MainWP is a self-hosted dashboard for managing many WordPress sites from one place, and its changelog is really a stream of independent extension updates — Google Search Console, Patchstack security, regression testing, cost and time tracking, analytics integrations. Recent work is squarely maintenance: reliability fixes to sync logic, batched multi-site operations, and UI consistency passes tied to the MainWP v6 interface. No single release reshapes the platform; the signal is breadth of ecosystem upkeep.
What is werf?
The 3.x line finally ships function: authenticated secret writes and render patches.
werf publishes the same work across alpha, beta, ea and stable channels plus a 3.x dev line, so one fix surfaces three or four times under different version numbers. This pair is that pattern exactly: v3.3.0 carries two features — writing authenticated secret values from deploy, and renderPatches support — plus four fixes, and v2.77.2 carries the same four fixes and nothing else. The fixes are the usual build-engine territory: buildah imports failing on symlinked paths, a panic when a stapel base image disappears mid-commit, a cache repo pointing at itself, and host-cleanup misreporting what it pruned.
MainWP vs werf: editorial side-by-side
MainWP
0.0INFRA · APIS
MainWP's pulse is a steady drip of per-extension maintenance, not headline features.
◆ Current state
MainWP is a self-hosted dashboard for managing many WordPress sites from one place, and its changelog is really a stream of independent extension updates — Google Search Console, Patchstack security, regression testing, cost and time tracking, analytics integrations. Recent work is squarely maintenance: reliability fixes to sync logic, batched multi-site operations, and UI consistency passes tied to the MainWP v6 interface. No single release reshapes the platform; the signal is breadth of ecosystem upkeep.
◆ Where it's heading
The pattern is a broad extension catalog kept individually current rather than a concentrated feature push — each extension gets fixes and small additions on its own cadence. Two themes recur: hardening multi-site operations at scale (batched Patchstack syncing, robust site mapping) and aligning every extension's UI with the v6 redesign. This is the maintenance profile of a mature product monetized through add-ons.
◆ Prediction
Expect continued per-extension point releases focused on reliability and v6 UI alignment, with the security (Patchstack) and analytics (GSC, Fathom) integrations seeing the most active work. A platform-level shift isn't visible in these entries.
werf
5.0INFRA · APIS
The 3.x line finally ships function: authenticated secret writes and render patches.
◆ Current state
werf publishes the same work across alpha, beta, ea and stable channels plus a 3.x dev line, so one fix surfaces three or four times under different version numbers. This pair is that pattern exactly: v3.3.0 carries two features — writing authenticated secret values from deploy, and renderPatches support — plus four fixes, and v2.77.2 carries the same four fixes and nothing else. The fixes are the usual build-engine territory: buildah imports failing on symlinked paths, a panic when a stapel base image disappears mid-commit, a cache repo pointing at itself, and host-cleanup misreporting what it pruned.
◆ Where it's heading
The division of labour between the lines is now explicit — 2.x takes only fixes, 3.x takes fixes plus everything new. This is the first window where the 3.x dev line carries user-facing deploy function rather than build internals and gated experiments, which moves it from a place to accumulate changes toward something with its own reason to exist. The build-engine hardening under parallelism continues underneath both.
◆ Prediction
renderPatches and authenticated secret writes are both deploy-side, so the next 3.x releases likely continue there rather than returning to buildah. Whether the embedded deno work behind its build tag connects to the render path is still not stated.
Alternatives to MainWP 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 MainWP or werf.
incident.io
Alert rate limits stop being per-source and start being per-tenant, by query.
Warp
The essay series keeps running ahead of the products it describes.
Node-RED
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
Infisical
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
Retool
Retool posts one-line changelog entries, and its agent work is the only visible thread
Recent activity from MainWP and werf
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agowerf3.3.0 adds authenticated secret writes and renderPatches to deploy
- 1d agowerf2.77.2 backports four build and cleanup fixes, no new function
- 22d agowerf2.77.1 fixes buildah imports on symlinked paths
- 22d agowerf3.x dev embeds deno and adds a registry-side cleanup report
- 23d agowerf2.76.0 adds condition-tracking gate and build timing
- 27d agowerflatest-signature
- 3mo agoMainWPMainWP Google Search Console Extension
- 3mo agoMainWPMainWP Patchstack Integration
- 8mo agoMainWPMainWP Early Access Extension
- 1y agoMainWPMainWP Regression Testing Extension
- 1y agoMainWPMainWP Time Tracker Extension
- 2y agoMainWPMainWP Cost Tracker Assistant Extension
Frequently asked questions
What is the difference between MainWP and werf?
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.
Is MainWP better than werf?
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.
What are the best alternatives to MainWP?
Top MainWP alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "MainWP alternatives" section above for the current picks, or visit /alternatives/mainwp 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.