How this writeup was made
Five products, ~25 sources: official product pages, hands-on reviews, real-family experience writeups, developer documentation where it exists, and community threads. Each source was downloaded as raw HTML, parsed into searchable chunks, and used as a citation backbone for the comparison.
Every claim in the comparison table traces back to a specific source. The research notes (the matrix, citations list, and rationale) live in our project files if you ever want to see what we found and where.
The interesting catch
While researching Skylight Calendar, the first surface-level result for "Skylight API documentation" looked official — pages at support.skylight.global with developer documentation. But reading the actual page content revealed it's for a different company entirely: an AI lab whose product is also called Skylight and tracks maritime vessels by satellite. They are unrelated companies that share a brand name.
A faster surface check would have happily asserted "Skylight Calendar has an official API." It doesn't. The reverse-engineered community wrapper that does exist (npm package called @eaglebyte/skylight-mcp) talks to undocumented internal endpoints and could break with any Skylight update.
Worth flagging because this is the kind of small thing that changes a recommendation — an "official API" would have put Skylight in the running on the differentiator question.
What this writeup does not claim
- It does not claim DAKboard is the best product on most dimensions. It wins narrowly on the custom-content question; it loses on price, ease, and chore-system to other products.
- It does not claim Hearth is bad. The reviews are very positive for what Hearth does. It just doesn't do the thing we asked about.
- It does not claim Nest Hub Max is bad. It's the cheapest hardware in the group, Face Match is novel, and it's the right tool for a Google-Home household. It's just not the right tool for putting our own content on the wall.
- It does not recommend a specific purchase path. Whether to buy at all, when, and where is for us to decide together.
Sources, in brief
For each of the five products we looked at: the official product page, at least one long-form independent review (Wirecutter-class), at least one community thread (Reddit or vendor community), and the developer documentation where it exists. Two cross-product comparison pieces were included for sanity. Three pages were initially blocked by anti-bot measures and were re-fetched via a browser-emulation tool. Full source list is in the project files.