Secure remote access / Work project · production deployment
Vipsy.
Remote Home Assistant access, without exposing the local network.
PythonDockerTLSReverse proxyWebRTC / coturn
PRODUCTION / HOME ASSISTANT OS
BUILT FOR THE PLACE IT RUNS
On-site systems. Not a hosted website.
Deployed with Home Assistant at the property. It is not a standalone website: the gateway needs an HAOS host and the live site’s network environment.
Maintained across 10+ production sites in IndiaRésumé-reported deployment context
LIVE SYSTEM / CONCEPTUAL MAP HOSTED AT THE SITE
01
⌁
REMOTE CLIENTSYSTEM EDGE
02
◈
VIPSY GATEWAYSITE SERVICE
03
⌂
HOME ASSISTANTLOCAL ENDPOINT
TLS · AUTHENTICATED · SCOPED PROXY
▤
HOME ASSISTANT OS HOSTOn-site compute · configured network · connected devices
SITE-BOUND
Application access crosses the gateway; the private LAN stays private.
INTERACTIVE WALKTHROUGH / 01
Choose a control and see how the system’s ideas fit together.
vipsy / interactive studyLOCAL PREVIEW
PRIVATE NETWORK / APPLICATION-LEVEL PATH
01 / CLIENTHome appAuthenticated request
→ TLS →
02 / GATEWAYVipsyTerminates TLS · checks access
→ scoped proxy →
03 / SERVICEHome AssistantApplication endpoint
OPTIONAL MEDIA PATH
Architecture study · no remote connection is opened by this page.
THE ENGINEERING QUESTION / 02
How do you enable secure access from outside the home without exposing the home network or requiring a VPN app?
A secure application-layer gateway for Home Assistant. It terminates TLS, proxies authenticated requests to Home Assistant Core, and can relay WebRTC media through coturn.
THE APPROACH / 03
Make the system’s logic visible.
Put a purpose-built gateway at the application boundary. Let it terminate TLS and proxy only to the intended Home Assistant service, with a separate relay path for media when needed.
A CLOSER LOOK / 04
From the first input to a useful outcome.
This sequence summarizes the project’s core idea. The interactive panel is a local visual study; use the linked repository or live service for the implemented project.
01 →
Authenticate
A remote request enters through the gateway over TLS and is authorized for the application.
02 →
Proxy narrowly
Forward application traffic to Home Assistant Core instead of joining or exposing the private LAN.
03 →
Relay media
Use an optional WebRTC / coturn path for real-time media when the session needs it.