Nabu Casa remote access: authentication and alternatives
How Nabu Casa exposes a Home Assistant login, what its security controls provide, and how to compare other access options.

Nabu Casa remote access makes a Home Assistant installation reachable through a public URL. It uses Home Assistant's authentication rather than requiring a separate sign-in gateway before the login page can be reached.
For some users, that is an acceptable design. For others, especially those who require an external identity provider or private network access, it is a reason to consider a different setup.
A public login page is not itself a vulnerability. This post looks at what is exposed and where authentication takes place.
A hard-to-guess address is still public
Nabu Casa assigns each installation a URL. The address may look random, but that should not be treated as an access control. DNS enumeration tools can discover hostnames, and a reachable login page can be identified without knowing its address in advance.
For example, ProjectDiscovery's Subfinder can collect subdomains:
subfinder -d ui.nabu.casa -o subdomains.txt -r 1.1.1.1
A DNS record alone does not establish that a service is running. HTTPX can check responses and report properties such as the status code and page title:
httpx -l subdomains.txt -status-code -title -tech-detect -server -csv -o results.csv
These commands describe the method used in the original investigation. This edited article does not present the old scan totals as a current measurement. Use testing tools only where you have appropriate authorisation.
The practical point is that a public endpoint should rely on its authentication and maintenance, not on the assumption that nobody will discover it.
What Nabu Casa protects
Nabu Casa's security documentation describes end-to-end encryption. The TLS private key remains on the Home Assistant system. The service also blocks certain known-insecure Home Assistant versions.
Home Assistant supports multi-factor authentication, and Nabu Casa recommends enabling it for every user.
The distinction is where the login happens. Remote access presents the Home Assistant login and authentication endpoints to the internet. It does not add a separate SSO gateway in front of them. If an external gateway is a requirement, this model does not meet that requirement on its own.
That is different from saying that the traffic is unencrypted or that Home Assistant has no authentication. Neither would accurately describe the service.
Decide what your installation needs
Home Assistant may control lights and temperature sensors, or it may also connect to locks, alarms and cameras. Consider the consequences of account access in your particular setup.
Use strong credentials and MFA, keep the installation maintained, and review who has access. A publicly reachable service places particular importance on those controls. Adding another access service does not remove the need to protect the accounts used by that service.
Nabu Casa also supports the Home Assistant project and provides Google Assistant and Amazon Alexa integrations. Those benefits are part of the choice. The question is whether its access model fits your requirements.
Other remote access options
Homeway
Homeway is another remote access option. If you are considering it for an additional sign-in step, check its current documentation for supported identity providers, MFA behaviour and which endpoints remain reachable.
This article does not establish that one provider is universally safer than another. Compare the authentication path and account recovery process you will actually use.
Tailscale
Tailscale can provide private network access between authenticated devices. It uses WireGuard and supports MFA through the configured identity provider. Its identity documentation explains that relationship.
That can suit someone who wants to reach Home Assistant through a private network rather than publish its login page. It also means managing the devices, accounts and access rules that belong to that network.
Choose an access model you can maintain
Start with who needs remote access and which devices they will use. Then decide whether direct Home Assistant authentication, an additional sign-in service or a private network meets those needs.
Whatever you choose, document how access is granted and removed. Check the assumptions again when adding users or connecting more sensitive devices.
Contact us if you want help reviewing your Home Assistant access setup or implementing a specific authentication requirement.
