Short Answer: No, Home Assistant Works Without Nabu Casa. Cloud Just Removes Friction.

Home Assistant's own Cloud documentation is explicit: Home Assistant Cloud is optional, and Home Assistant works fully without it. Your dashboards, automations, Zigbee or Z-Wave radios, device integrations, and local control still run on the hardware in your home.

What Nabu Casa buys is convenience for the parts that are tedious to build and maintain yourself: secure remote access, the shortest Alexa and Google Assistant setup path, cloud speech services for Assist, and an off-site latest-copy backup. If you are comfortable operating your own VPN, hostname, SSL, and developer-console setup, you can skip it. If you want the house to keep working without turning yourself into permanent support, Cloud is often worth it.

Tara's rule: buy Home Assistant Cloud for supportability and convenience, not because your local automations need permission to run.

Why This Question Keeps Coming Up

The demand is current, not hypothetical. On April 2, 2025, a new Home Assistant Community user asked how to use Alexa without Nabu Casa and immediately ran into the AWS and developer-account reality. On March 3, 2025, another thread compared Nabu Casa vs Tailscale because both can solve remote access but do not solve the same surrounding problems.

Reddit shows the same pressure from a different angle. In a thread published about September 2025, one user wanted voice control for their mom and guests without adding another subscription. In another thread from about December 2025, a user asked whether Nabu Casa would make Alexa automations and remote iPhone access easy, and the immediate answer was essentially yes.

Inference from those sources: people are usually not asking whether Home Assistant can technically function without Cloud. They are asking who has to own the remote-access, voice-assistant, and family-support glue.

What Still Works Without Nabu Casa

If your goal is a local smart home, most of the important parts do not depend on Nabu Casa.

Goal Without Nabu Casa What Cloud changes
Local dashboards and automations Already local. No subscription required. No change to where the logic runs. It still runs in your home.
Remote app access Use a VPN such as Tailscale or ZeroTier, or maintain your own HTTPS endpoint. Single-toggle remote URL, encrypted traffic, and no router port changes.
Alexa integration Use Home Assistant's manual Alexa setup with Amazon developer tooling and usually AWS Lambda. Turns Alexa exposure into a few-click flow.
Google Assistant integration Use Home Assistant's manual Google Assistant setup with a public hostname, SSL, and Google Home Developer Console work. Turns Google Assistant setup into a few-click flow.
Voice in the house Run focused-local or full-local Assist with Speech-to-Phrase, Whisper, and Piper. Adds cloud STT/TTS services and an easier cloud voice path.
Backups Use network shares and other backup locations. Since February 5, 2025, Home Assistant also supports Google Drive and OneDrive backup integrations. Adds one encrypted off-site latest backup up to 5 GB.
Household handoff Fine for one technical owner if you maintain it. Usually calmer for spouses, guests, and remote troubleshooting.

The important nuance is that "without Nabu Casa" is not the same as "without cloud." If you manually wire Home Assistant into Alexa or Google Assistant, you are still using Amazon or Google cloud services. If your actual goal is fully local voice, that is a different path entirely, and Home Assistant's June 25, 2025 voice roadmap explicitly lays out focused-local and full-local options.

What Nabu Casa Actually Adds

The current Home Assistant Cloud and Nabu Casa support docs describe a fairly tight feature bundle:

  • Secure remote access to your Home Assistant instance.
  • Easy voice-assistant integration for Assist, Alexa, and Google Assistant.
  • Improved text-to-speech and cloud speech-to-text options.
  • Cloud storage of your latest Home Assistant backup.
  • Webhooks for automation triggers.
  • Improved camera streaming with WebRTC.

The remote-access value is the most obvious. The official remote-access docs say the easiest and safest option for most people is Home Assistant Cloud, and that it gives you a unique remote URL with encrypted traffic and no port forwarding. The security guide repeats the same recommendation and explicitly says to use a secure remote-access method rather than exposing Home Assistant directly to the internet.

The voice-assistant value is the second major reason people subscribe. The Alexa docs say Cloud avoids the dynamic DNS, SSL, and router-port work that manual Alexa setup needs. The Google Assistant docs say the manual path requires an externally accessible hostname with SSL plus Google Home Developer Console configuration. That is exactly the kind of setup advanced users can do, but beginners often do not want to operate.

Remote Access Is the Real Decision Boundary

For many homes, the real question is not Cloud versus no Cloud. It is managed remote access versus DIY remote access.

Home Assistant's docs recommend VPN first when you want a self-managed remote path. Tailscale is a very good answer when one technical owner wants private access from their own devices. That is why the community keeps comparing Tailscale and Nabu Casa directly.

But Tailscale and Nabu Casa do different jobs. The March 3, 2025 community discussion summarized it well: Tailscale is a VPN path, while Nabu Casa is the easier remote-access path that also lines up with Google, Alexa, voice, and remote storage. If you only need your own phone and laptop to reach the dashboard, Tailscale may be enough. If you want the same home to work for less technical family members and voice ecosystems, Cloud is usually the calmer choice.

Privacy and Security Boundaries

There are two misconceptions worth killing early.

First: Home Assistant Cloud does not move your automations into the cloud. Home Assistant's own Cloud page says the cloud service exists for things that genuinely benefit from a cloud connection while everything else continues to run locally on your own hardware.

Second: Nabu Casa says it does not have access to your Home Assistant instance. Its support docs say the connection is established from your Home Assistant instance outward, messages stay encrypted, and the company has no administrative tools to log back into your system. Its remote-access security page also says traffic stays end-to-end encrypted from your instance to your device.

That said, remote access is still remote access. Home Assistant's security guide says to use a strong unique password and turn on multi-factor authentication for user accounts. The Nabu Casa security page adds the same practical warning: if your instance is reachable from the wider internet, credential hygiene still matters. Cloud reduces infrastructure burden; it does not eliminate account security responsibility.

Privacy line to remember: if your household goal is zero cloud voice, skip Alexa and Google entirely and build around fully local Home Assistant voice. "No Nabu Casa" alone does not automatically mean "no cloud."

Which Path Fits Which Home

  1. Single technical owner, privacy-first: skip Nabu Casa, use Tailscale or another VPN, build local voice, and keep off-site backups through a second backup location.
  2. Family home with Alexa or Google already in the house: buy Nabu Casa. The reduced setup and support burden is usually the real win.
  3. Installed local system that still needs easy handoff: a hybrid is reasonable. Keep automations, radios, and most logic local, but use Cloud for remote access and voice-assistant exposure.
  4. Backup-conscious household: do not rely on Cloud backup alone. Use Home Assistant Cloud as one off-site copy and keep a second backup destination too.

Tara's Take

The wrong framing is "Is Nabu Casa required?" The right framing is "What support job am I trying to avoid?"

If the answer is "none, I like owning the stack", skip it. Home Assistant gives you the tools to do that. If the answer is "I want my phone, my partner's phone, the guest speaker, and the backup path to stay boring", Cloud is a reasonable operating choice, not a betrayal of a local smart-home philosophy.

Tara's bias is local-first, private-first, and supportable. That usually means local automations by default, Cloud only where it lowers household risk, and a design that still works when one person is not around to debug a certificate or broken OAuth flow.

If this question is on your mind, these adjacent guides usually matter next.

FAQ

Does Home Assistant work without Nabu Casa?

Yes. Home Assistant's own Cloud page says Home Assistant works fully without Home Assistant Cloud. The subscription is optional and mainly changes how easily you handle remote access, cloud voice integrations, and a few convenience features.

Do I need Nabu Casa for Alexa or Google Assistant?

No, but it is the easiest path. Home Assistant documents manual Alexa and Google Assistant setups without Cloud, but both require more infrastructure and developer-console work than most homeowners want to own long-term.

Do I need Nabu Casa for local voice?

No. Home Assistant's current voice roadmap supports focused-local and full-local voice paths using local speech and text-to-speech engines. If strict privacy is the goal, that is the path to follow.

Is Home Assistant Cloud backup enough by itself?

It is useful, but it is not the whole backup plan. Current docs say Cloud stores one encrypted backup up to 5 GB. That makes it a strong latest-copy safety net, not a complete archival strategy by itself.

Is Tailscale better than Nabu Casa?

Sometimes. Tailscale is excellent for one technical owner who wants private remote access. Nabu Casa is usually better when the home also wants Alexa or Google, easier phone setup for multiple people, or lower maintenance overall.