Start Free
For Home Assistant on hardware you own

Home Assistant Remote Access — Without Port Forwarding

Install the add-on inside Home Assistant, paste one key, and reach your dashboard on a normal HTTPS address from any browser. Nothing to open on the router, nothing to install on the phone or laptop you connect from, and it works behind CGNAT.

Start Free See the three steps

Free forever tier · No email or credit card required

What people usually try first

  • Port forwarding plus DuckDNS — and an open port on the home router
  • A VPN, which means installing a client on every device you connect from
  • Cloudflare Tunnel, which wants your domain’s DNS moved to them
  • Nothing works at all on mobile broadband or any CGNAT connection
  • Certificates expire, the public IP changes, the bookmark breaks

What Pluggie does instead

  • A Home Assistant add-on — install, paste the key, done
  • The router stays closed; the agent dials outward
  • Open a normal HTTPS address in any browser, on any device
  • Your own domain on the paid plan, one CNAME, registrar unchanged
  • The same hostname after a restart, a reboot or a new public IP
Why it works

Built for a Home Assistant that has to stay reachable

Home Assistant runs on your hardware and your data stays there. The only thing Pluggie changes is how you reach it from outside.

🏠

Installs as an add-on

Add the repository in Home Assistant, install the Pluggie add-on and paste the access key from your dashboard. If you run Home Assistant Container instead, the same agent runs as a Docker container.

🔒

No open ports, no router config

The agent makes an outbound connection, so nothing is forwarded and nothing is exposed. That is also why it works behind CGNAT, where port forwarding is not possible at all.

📱

Nothing to install to connect

You open an ordinary HTTPS link in any browser — a work laptop, a borrowed phone, a machine where you have no administrator rights. Only the machine running Home Assistant runs the agent.

🌐

Your own domain, included

Point a CNAME and keep your registrar and nameservers where they are. Included on paid plans from $6/month rather than billed as an extra.

🌎

Locked down by country and IP

Restrict the tunnel to the countries and IP ranges you actually use. Everyone else gets nothing, which matters when the thing behind the address controls your home.

🔐

Certificates on your device

Certificates are generated on your hardware and the relay never decrypts what passes through it. Automatic SSL, nothing to renew by hand.

Not only Home Assistant

The same account carries the rest of the house

Home Assistant is usually the first tunnel people create. It is rarely the last: a NAS web interface, camera dashboards, Proxmox, Jellyfin, a Docker service — anything with a web interface works the same way. If you also run a NAS or a home server, the home server page covers that side, and compare alternatives puts Pluggie next to Nabu Casa, ngrok, Cloudflare Tunnel and Tailscale.

Setup

Three steps, about five minutes

1

Create a free account

No email address and no card. You get an access key and one tunnel straight away.

2

Install the add-on and paste the key

Add the Pluggie repository in Home Assistant, install the add-on, paste the key and start it. Running Home Assistant Container? Use the Docker container instead and point it at http://homeassistant.local:8123.

3

Open it from anywhere

Your dashboard is live on its own HTTPS address with a valid certificate. Bookmark it, put it in the companion app, and it is still the same address after a reboot.

Questions

Home Assistant remote access, answered

Install the Pluggie add-on from inside Home Assistant, paste the access key from your dashboard and point a tunnel at your Home Assistant instance. The agent dials outward, so nothing is opened on the router. You then reach Home Assistant on a normal HTTPS address from any browser.
No. You open an ordinary HTTPS link in any browser - a work laptop, a borrowed phone, a machine where you have no administrator rights. Only the machine running Home Assistant runs the agent. That is the main difference from a VPN, which needs a client on every device you connect from.
Yes. Because the agent makes an outbound connection, no public IPv4 address and no forwarded port are needed. That is also why it works on mobile broadband and other connections where port forwarding is impossible.
Nabu Casa is made by the Home Assistant project and is the natural choice if Home Assistant is the only thing you want to reach and you want cloud voice assistants and official support. Pluggie is not tied to Home Assistant - the same account also carries your NAS, cameras, Proxmox or anything else with a web interface - and it lets you use your own domain.
Yes, on the paid plan. You point a CNAME at Pluggie and keep your registrar and nameservers exactly where they are. There is no DNS transfer and no nameserver change.
Yes - one tunnel with 1 GB at full speed per 30 days, and it needs no email address and no credit card. After the cap it throttles rather than cutting you off.
Yes. Every tunnel can be limited by country with GeoIP filtering and by IP range, so the address is only reachable from where you actually are. Certificates are generated on your device and the relay never decrypts the traffic passing through it.
No. The hostname is assigned once and stays yours through restarts, reboots and a changing public IP, so bookmarks and companion apps keep working.

Reach Home Assistant from anywhere

Free tier, no email, no card. Five minutes from add-on to a working HTTPS address.

Start Free