Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
A side-by-side editorial comparison of Dokploy and Merge — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Dokploy | Merge |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | self-hosted-paas, secrets-encryption, security-hardening, plan-limits | unified api, agent handler, mcp connectors, ai gateway |
| Last editorial update | 12d ago | 12h ago |
| Website | Visit → | — |
A self-hosted PaaS spending its releases on secrets, injection fixes and plan limits.
Dokploy cuts patch releases every one to two weeks, and the recent stream is dominated by hardening rather than features. v0.29.12 added AES-256-GCM encryption for environment variables at rest and made backups carry the full keyring; v0.29.13 closed an OS command injection in git clone across all providers. The newest tag says outright that it is bug fixes only. Alongside that, plan limits landed in v0.29.10.
Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.
Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.
Dokploy cuts patch releases every one to two weeks, and the recent stream is dominated by hardening rather than features. v0.29.12 added AES-256-GCM encryption for environment variables at rest and made backups carry the full keyring; v0.29.13 closed an OS command injection in git clone across all providers. The newest tag says outright that it is bug fixes only. Alongside that, plan limits landed in v0.29.10.
The direction is a self-hosted platform trying to earn production trust: encrypted secrets, injection fixes, a pinned install script tied to each release, and Postgres query rewrites to stop hitting the 100-argument limit on rollbacks, schedules and backups. Plan limits point the other way — toward a commercial tier layered on the open-source core. Both arcs suggest the project is past feature-chasing and into making the platform defensible.
Expect the hardening thread to continue into the rest of the 0.29 line, with the plan-limits work being the seed of a paid tier that gets more definition before a 0.30 release.
Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.
The through-line is that Merge is repositioning from data plumbing to the layer agents pass through. Each week adds either reach (more connectors, more tools per connector, more models) or control (guardrails, per-project policy, access configuration). This window is reach-and-efficiency: the GitHub connector expanded to 145 tools, Outlook payloads were cut substantially, and Gateway guardrails became configurable per project rather than per account.
Expect the per-project granularity applied to guardrails to spread to the rest of Gateway's controls, and the connector catalog to keep absorbing hosted third-party MCP servers the way Axiom was added.
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 Dokploy or Merge.
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
See all Dokploy alternatives → · See all Merge alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dokploy and Merge are shipping at a similar cadence (velocity 6.3 vs 6.3, 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dokploy and Merge are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Dokploy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dokploy alternatives" section above for the current picks, or visit /alternatives/dokploy for the full list with editorial commentary on each.
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.