Replace Home Assistant Cloud?
KINDA · weekend projectThe core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Home Assistant Cloud, self-host smart-home control and use a user-owned remote-access tunnel. The hard boundary is managed remote access, voice integrations, funding for open source, and low-maintenance security, plus sync, integrations, and household adoption.
Build a personal replacement for Home Assistant Cloud in an empty repository. Use Next.js 15, TypeScript, SQLite, Drizzle ORM, and a local-first PWA; do not offer alternative stacks. The core loop is: self-host smart-home control, reach it remotely through a user-owned tunnel, and keep automation data portable and owner-controlled. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create household members, shared lists, calendar items, recipes or inventory records, and assignments. Provide fast mobile-first capture with large controls, offline queueing, and conflict-safe sync to one server. Support recurring chores or events, reminders, completion history, and printable views. Add CSV or JSON import and export plus photo attachments with clear size limits. Allow private and shared items and make every change attributable and undoable. Add backups, household export, member removal, and a simple invite code. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out retailer ordering and proprietary product catalogs. Deliberately leave out broad smart-home integrations. Deliberately leave out large public recipe libraries and polished native mobile clients. Finish by running the tests and listing the exact commands used.
$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR
People still pay for Home Assistant Cloud because household apps survive when every family member actually uses them and the data stays current across devices. The recurring cost buys multi-user conflicts, reminders, notifications, imports, barcode data, smart-home APIs, backups, and long-term maintenance, not just the visible interface.
xmanaged remote access, voice integrations, funding for open source, and low-maintenance security
xfrictionless family sync
xretailer and smart-home integrations
xlarge recipe or product database
xmobile polish
What does the Home Assistant Cloud verdict mean?
The core job looks buildable, with meaningful gaps: managed remote access, voice integrations, funding for open source, and low-maintenance security, frictionless family sync. Read the full tradeoff list before committing. This research record is not a hosted IVCIFY tool.
What price does this directory record show for Home Assistant Cloud?
The directory records $7.5/month for Cloud, checked 2026-07-31. Verify the source before making a purchase decision. This reference stays outside retail Stack Math unless current matched evidence supports the comparison.
What do I lose by replacing Home Assistant Cloud?
Honestly: managed remote access, voice integrations, funding for open source, and low-maintenance security; frictionless family sync; retailer and smart-home integrations; large recipe or product database; mobile polish. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Home Assistant Cloud?
The listed prior art includes Mealie (Active open-source recipe manager and meal planner for households.). Inspect those projects before starting from a blank prompt.