GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of Obsidian and Wazuh — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Obsidian | Wazuh |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | cli, local-first, desktop-client, release-rollups | siem, endpoint-security, open-source, security-hardening |
| Last editorial update | 3mo ago | 8h ago |
| Website | — | Visit → |
Obsidian's feed has gone quiet: version pointers up top, the bundled CLI the last real move.
The four most recent entries are pointers, not release notes — each says only that the build includes everything up to Obsidian Desktop v1.13.1 through v1.13.4, with no description of what actually changed. The last substantive work visible in this window is from March, when the installer started bundling a dedicated CLI binary instead of invoking the Electron executable, cutting terminal round-trip time and adding shell autocompletion for Obsidian commands. Everything published since is content-free rollup text.
Wazuh hardens its 4.14 line while 5.0 rebuilds how agents talk to the manager.
Wazuh ships 4.14 patch releases roughly every two to three weeks, and almost all of the content is security hardening: path traversal and command injection fixes, input validation in the cluster code, connection deadlines and memory leak fixes. 4.14.10 also added memory limits for oversized rulesets and queue warnings for the vulnerability scanner. In parallel, 5.0.0 reached its second release candidate on October 30.
The four most recent entries are pointers, not release notes — each says only that the build includes everything up to Obsidian Desktop v1.13.1 through v1.13.4, with no description of what actually changed. The last substantive work visible in this window is from March, when the installer started bundling a dedicated CLI binary instead of invoking the Electron executable, cutting terminal round-trip time and adding shell autocompletion for Obsidian commands. Everything published since is content-free rollup text.
Treat the CLI work as the signal and the rollups as noise: a first-class terminal entry point is what lets external tools and scripts drive a vault, which is the difference between a local-first notes app and a substrate other software can build on. The follow-up entries — a macOS path check and a hidden socket dotfile — show the CLI being hardened for real cross-platform use rather than shipped and abandoned. Meanwhile this feed itself has stopped carrying detail, deferring to the desktop release notes it points at.
The visible thread is CLI and TUI ergonomics, so continued work on that surface is the safest read; nothing in these entries supports a confident call beyond it. What is genuinely unclear is whether this feed resumes describing releases or stays a pointer to the desktop changelog.
Wazuh ships 4.14 patch releases roughly every two to three weeks, and almost all of the content is security hardening: path traversal and command injection fixes, input validation in the cluster code, connection deadlines and memory leak fixes. 4.14.10 also added memory limits for oversized rulesets and queue warnings for the vulnerability scanner. In parallel, 5.0.0 reached its second release candidate on October 30.
5.0 is the real change: agents move to HTTPS for talking to the manager, a new detection engine replaces the 4.x analysis daemon, and every server install becomes a cluster node. The 4.14 branch, meanwhile, reads like a security audit being worked through release by release, which keeps current installs safe while 5.0 settles.
More 5.0 release candidates are likely before a final release, and 4.14 patch releases with security fixes should keep coming every few weeks; a 5.0 GA date is not stated in these entries.
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 Obsidian or Wazuh.
GravityKit folds every GravityView extension into one Pro plugin.
Payload's v4 beta.9 keeps every past image crop and raises the Node floor again.
Nautobot 3.3 alpha 2 adds test helpers and a cable location filter after 3.2.9's token-leak fix.
Clair 4.10 RC can read SBOMs to match Java vulnerabilities.
Shuffle tags builds almost daily, but the notes are empty.
KrakenD's community edition is shipping only dependency bumps.
See all Obsidian alternatives → · See all Wazuh alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Obsidian and Wazuh 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Obsidian and Wazuh 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.
Top Obsidian alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Obsidian alternatives" section above for the current picks, or visit /alternatives/obsidian for the full list with editorial commentary on each.
Top Wazuh alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Wazuh alternatives" section above for the current picks, or visit /alternatives/wazuh for the full list with editorial commentary on each.