Dashy
Dashy shipped ten releases in five days; one fixes how auth headers trust origins
A side-by-side editorial comparison of Home Assistant and PDFMonkey — release velocity, themes, recent moves, and the top alternatives to consider.
Home Assistant keeps pulling hidden power-user features into the UI, now trigger IDs.
Home Assistant ships one release a month, each built around a friction point that used to need YAML or a buried menu. 2026.10 gives trigger IDs a proper UI, so one automation can branch on several triggers without hand-written IDs, and replaces the map with a vector OpenStreetMap after the old provider started requiring an API key. It also adds a Modbus connections panel, one-click AI connection and 15 new integrations.
PDFMonkey adds an MCP server and Node.js SDK, so assistants can generate its documents.
An October 26 catch-up lists what shipped since summer. New items are zero-downtime API key rotation with a two-day overlap, snippet folders, an official Node.js SDK and an MCP server for Claude, Cursor and other AI assistants. Zapier document generation no longer races the 30-second limit, and n8n node 1.0 is now verified by n8n. February's visual builder remains the largest change in this window.
Home Assistant ships one release a month, each built around a friction point that used to need YAML or a buried menu. 2026.10 gives trigger IDs a proper UI, so one automation can branch on several triggers without hand-written IDs, and replaces the map with a vector OpenStreetMap after the old provider started requiring an API key. It also adds a Modbus connections panel, one-click AI connection and 15 new integrations.
The 2026 run reads as a single program: infrared in April, radio frequency in May, purpose-specific triggers by default in July, shared Modbus connections in September, trigger IDs in October. Each release takes something experts already had and makes it findable. Nabu Casa is also renaming Home Assistant Cloud to Home Assistant Link, planned for the December release.
The Cloud-to-Link rename is scheduled for the December release, so expect it there; the November release will most likely take on another automation or dashboard feature that still needs YAML.
An October 26 catch-up lists what shipped since summer. New items are zero-downtime API key rotation with a two-day overlap, snippet folders, an official Node.js SDK and an MCP server for Claude, Cursor and other AI assistants. Zapier document generation no longer races the 30-second limit, and n8n node 1.0 is now verified by n8n. February's visual builder remains the largest change in this window.
The two-audience pattern holds, and a third has joined: AI assistants calling PDFMonkey directly. The builder serves non-developers, while the SDKs, key rotation and automation fixes serve teams with PDFMonkey in production. Work on Zapier and n8n shows attention to where documents are actually triggered.
Expect more integration and SDK coverage, given the Ruby and Node.js releases and the n8n and Zapier work. How MCP use develops is not readable from a single catch-up post.
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 Home Assistant or PDFMonkey.
Dashy shipped ten releases in five days; one fixes how auth headers trust origins
Mergify's merge queue now hunts the breaking PR by rerunning failed tests first
Fluentd 1.20 drops its yajl dependency to keep building on Ruby 4.1
WorkOS spent October giving IT admins control of Pipes and audit trails
ClouDNS widens its SSL catalog and adds maintenance windows to monitoring
fossa-cli's feed jumps from 3.17 to 3.20, with clearer container scan errors.
See all Home Assistant alternatives → · See all PDFMonkey alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Home Assistant and PDFMonkey are shipping at a similar cadence (velocity 2.5 vs 2.5, 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. Home Assistant and PDFMonkey are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Home Assistant alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Home Assistant alternatives" section above for the current picks, or visit /alternatives/home-assistant for the full list with editorial commentary on each.
Top PDFMonkey alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PDFMonkey alternatives" section above for the current picks, or visit /alternatives/pdfmonkey for the full list with editorial commentary on each.