Home Assistant,
hosted properly.
A hosted Home Assistant instance per household. No home server, no port forwarding, no DIY. Built in Sweden, ready to launch, not yet trading.
Home Assistant, hosted — without the home server.
VomeHome Lead product
One isolated HAOS VM per customer, connected to the home over an outbound WireGuard tunnel.
Backup & failover
Customers can boot a hosted backup onto a local Pi or NUC, or vice versa. Portable in both directions, by design.
VomeSync — companion
Small open-source integration for multi-home switch networks. Not the headline; useful for the upsell.
Home Assistant is bigger than most people realise.
Active installations crossed a million in 2024 and the Open Home Foundation now reports figures comfortably above that. Self-hosting suits the enthusiasts well. The rest want the same capabilities without running a server themselves — and currently default to a closed hub.
The same Home Assistant, for three under-served groups.
Self-hosting works wonderfully and we support it actively. The opportunity is the rest of the market.
Hands-off households
Want a smart home, don't want a server in it. Currently default to a closed hub.
Multi-property owners
Holiday lets, parents' houses, annexes, small offices. One server per house is impractical.
Self-hosters with a safety net
Boot a hosted instance from backup if the Pi fails, you're away, or you want a sandbox.
VomeHome — managed Home Assistant.
What we provide
An isolated HAOS VM per customer. A WireGuard tunnel from a small adaptor at home (or an existing OpenWrt / GL.iNet router) reaches the LAN's devices. Every HA integration, add-on, blueprint and HACS module works unchanged.
Two-way portability
Boot from backup — in either direction. A self-hoster can use VomeHome as a hot-standby; a hosted customer can leave for a Pi at any time. We don't lock anyone in.
Three boxes, one outbound tunnel.
Customers sign in (GitHub today, email and passkey planned). Their Home Assistant runs in an isolated HAOS VM. A small adaptor at home holds a WireGuard credential and connects outbound to the host. From the customer's view, it's Home Assistant in a browser.
- Isolation: one VM per customer; no shared HA processes.
- Outbound only: nothing on the home LAN is exposed to the public internet.
- Standard HA: existing automations, add-ons, blueprints and integrations all keep working.
- Portable: one-click migration to or from a local Pi/NUC, by design.
Why HA — and where else this stack can go.
The smart-home space splits cleanly along two axes: open vs. closed ecosystem and plug-and-play vs. self-assemble. Closed hubs win onboarding; open platforms win control and integration breadth. The top-right is empty — that's where we sit. (Click the chart to enlarge.)
Why HA, specifically:
- Largest open ecosystem — ~1.4M active installs, 2,500+ integrations.
- Stable architecture — HAOS as a managed unit fits the hosting model.
- Active community — HACS, forums, blueprints; we plug into all of them.
- Expansion space. Once VomeHome is established, the same hosting / tunnel platform can host OpenHAB, ioBroker or Domoticz instances for those communities.
Where VomeHome sits in the existing market.
| Option | Hardware | Multi-home | Walled garden | Indicative cost |
|---|---|---|---|---|
| Self-hosted HA (Pi/NUC) | Yours to buy & maintain | One per home | No | ~800 SEK (€70) hardware + time |
| Nabu Casa Cloud | Still self-hosted | Single instance | No | ~85 SEK / month (€7.50) |
| Closed hubs (SmartThings, Apple Home, Alexa) | Vendor's | Limited | Yes | "Free" with lock-in |
| VomeHome | Ours; tiny adaptor in the home | Many homes per account | No — standard HA | 89–179 SEK / month (€8–€15) |
Nabu Casa solves remote access for self-hosters. We solve the hosting itself, and stay friendly to the open Home Assistant ecosystem rather than competing with it.
The platform is doing the heavy lifting we'd otherwise pay for.
The Open Home Foundation publishes its roadmap openly. The themes for the next year all play to a managed-HA provider rather than against one.
Auto-patching & E2E-tested releases
HAOS auto-patch and end-to-end testing of HA Core before release are both on the public roadmap. Both lower the operational risk of running customer instances at scale.
Smarter Assist + voice satellites
Memory, context-awareness and better STT for ESPHome voice satellites are queued. Voice is exactly the surface area non-technical households respond to — we ship it pre-configured.
Refined camera UI & PTZ
Cameras are the second-most-asked feature in our target segment. Better native support reduces the integration tinkering most casual users won't do themselves.
Nabu Casa stays in its lane
OHF's roadmap shows Nabu Casa investing in cloud visibility and Connect-Proxy onboarding — for self-hosters. Different lane to ours; we host the instance, they relay it. Worth watching: any move toward full-stack hosting (Project Blast).
Source: Open Home Foundation roadmap.
Three monthly tiers. Nothing complicated.
Solo
89 SEK / mo (≈ €8)
One home, baseline VM, daily backups, community support.
Family
169 SEK / mo (≈ €15)
Up to three homes, larger VM, longer retention, email support.
Pro
From 349 SEK / mo (≈ €30)
Five or more homes, priority support, SLA — small property managers.
Unit economics. A modern hypervisor comfortably runs ~30 light HAOS VMs per host. At ~115 SEK (€10) blended ARPU and ~700 SEK (€60) all-in host cost per month, a host turns positive at roughly three-quarters full. Adapter sales, a community-organisation directory and the optional VomeSync upsell sit on top.
A working demonstration, not yet a trading business.
Built and tested
- HAOS provisioning, isolated per customer
- WireGuard tunnel automation
- GitHub sign-in, billing scaffolding (Stripe)
- Custom domain support, SSL automation
- VomeSync companion integration + Node/Redis service in development environment
- Internal security review, GDPR pass, ops runbook
Awaiting incorporation & launch
- Vome AB to be incorporated in Sweden
- Production hosts (currently a single dev box)
- Public launch on r/homeassistant + HA forum
- HACS submission for the companion integration
- Boot-from-backup & one-click local fallback
- Optional second engineer once revenue justifies it
Framed as a demonstration on purpose: not having started trading keeps options open — Vinnova, Almi, EU programmes, friends & family, or institutional pre-seed.
First 18 months after launch.
Quiet launch
Vome AB incorporated. First production host online. ~50 paying customers from waitlist + the HA community.
HACS & growth
Polished onboarding. Companion HACS submission. ~250 paying customers target.
Multi-home & backup
Multi-home billing, boot-from-backup migration, EU + UK regions. ~750–1,000 paying customers target.
Cash-flow positive
Operating break-even on the conservative case. ESP32 companion device pilot. Possible expansion to OpenHAB hosting.
Numbers are deliberately modest targets. Detailed projections and sensitivities live in the business plan.
One founder, on purpose — for now.
Andrew (Andy) Lyeklint Hancock — founder
Full-stack engineer based in Örkelljunga, Skåne. Long PHP, Python/Django, Angular, Linux and AWS background; open-source as @adlh on GitHub. Designed and built the entire current Vome stack — Flask portal, HAOS provisioning, WireGuard automation, the VomeSync companion integration, and the public website. Focused on shipping rather than storytelling.
Vome AB — planned
Swedish aktiebolag, incorporated on closing whichever funding path we take. Headquartered in Sweden for tax, compliance and proximity to Nordic / European customers. Cap table kept simple, with a small option pool reserved for a first hire if we reach that point.
Plan: keep the team small and the product focused. A second engineer only when the work justifies it. No sales team in the first eighteen months.
Three sizes of cheque, three plans.
The same product works at very different scales. Pick the path that suits the cheque you'd like to write — the business plan sets each one out in detail.
Bootstrap
AB share capital only. Founder runs it part-time alongside other income; ~100–300 customers in year one; pleasant, low-risk side income.
- No external investors
- One small VPS / dedicated host
- Slow, sustainable growth
Friends & contacts
Small SAFE or convertible from a known investor or two. One year of focused founder runway, one production host, no other hires. Targeting ~750–1,000 customers in 18 months.
- Cap table stays simple
- Founder full-time on Vome
- Preserves grant / pre-seed optionality
Pre-seed round
Range: 1.15–2.9 mln SEK (€100–€250k). Two production hosts, multi-region from day one, second engineer at month 6. ~6,000 customers in three years.
- Faster path to scale
- Structured reporting / governance
- For investors who'd rather we move quickly
Indicative SEK→EUR conversion at ~11.50 SEK / €1.
If any of this lands, drop me a line.
I'd rather have a frank conversation than send reams of documents. The business plan sets out the three paths in detail; the financial model, full code base and demonstration access are on request, under NDA where appropriate.
Demonstration & companion code
staging.vome.io ·
sync.vome.io
VomeHome source: available on request.
VomeSync companion: GitHub.
© 2026 Andrew Lyeklint Hancock / Vome (in formation). This deck is confidential and intended for the named recipient.