Casdoor
Casdoor is spending its release cadence moving auth checks from the client to the server
A side-by-side editorial comparison of DNSControl and Dokploy — release velocity, themes, recent moves, and the top alternatives to consider.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
DNSControl has locked v5.0.0 to bugfixes only with a stated ship date of 25 August 2026. rc9 carries no new capability: punycode decoding before IDNA validation in ALIDNS, a SVCB fix in POWERDNS, NAPTR and trailing-dot fixes in DYNU, a dnssort edge case, and internal refactors replacing pkg/diff and standardising on models.Records. The release notes read as a call for provider testing more than an announcement.
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.
DNSControl has locked v5.0.0 to bugfixes only with a stated ship date of 25 August 2026. rc9 carries no new capability: punycode decoding before IDNA validation in ALIDNS, a SVCB fix in POWERDNS, NAPTR and trailing-dot fixes in DYNU, a dnssort edge case, and internal refactors replacing pkg/diff and standardising on models.Records. The release notes read as a call for provider testing more than an announcement.
The v5 arc has run its course in public: rc1 laid out the dnsv2.RDATA refactor, rc3 finished converting every provider to it, rc4 completed the move to the Codeberg-hosted miekg/dns, and rc8 declared feature completeness. What is left is per-provider correctness on record types that only a handful of users exercise, which is why the maintainer is publishing a list of which providers most need testing rather than shipping.
Expect one or two more release candidates of provider fixes before the 25 August date, with the risk concentrated in providers nobody volunteers to test - the notes already flag PACKETFRAME as unmaintained and EXOSCALE as not supporting PTR.
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.
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 DNSControl or Dokploy.
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
NetBox adds a cooling data model — the first new infrastructure domain since power
Two parallel trains, and the 'maintenance' label is now hiding real feature work
See all DNSControl alternatives → · See all Dokploy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dokploy is currently shipping more aggressively (velocity 6.3 vs 5.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. Dokploy is currently shipping more aggressively (velocity 6.3 vs 5.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 DNSControl alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "DNSControl alternatives" section above for the current picks, or visit /alternatives/dnscontrol for the full list with editorial commentary on each.
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.