Ingress option for non addons

[ocueye2]

Describe the feature

I would like the ability to use the home assistant ingress for webservers on my lan that are not a home assistant addon.

Use cases

It allows me to use other services I host on my lan in home assistant whether I am on my lan or off my lan.

Current workarounds

I can use a dedicated load balencer with an auth page or just port forword each item

Anything else?

No response

[mik-laj]

The idea makes sense from a usability point of view, but it’s very unlikely to be added to the Home Assistant core or Supervisor. The ingress system was specifically designed for add-ons managed by the Supervisor, and extending it to arbitrary LAN services would break some key architectural and security boundaries.

A few reasons why this can’t realistically be part of the core:

• Security scope: Ingress relies on Home Assistant’s authentication and token system. Routing arbitrary external web services through that would mean HA takes responsibility for their cookies, CORS headers, CSRF handling, and authentication isolation — which would create serious risk if any of those services are misconfigured.

• Lifecycle management: Supervisor manages add-ons end-to-end (install, update, health checks, network isolation). Exposing unrelated services would bypass that model and make HA responsible for things it doesn’t control.

• Configuration complexity: Every web app behaves differently — path rewrites, WebSockets, static files, redirects, etc. Supporting all those edge cases safely and reliably would require a full reverse-proxy framework inside Supervisor.

For setups like yours, the practical route is to use a lightweight reverse proxy (Nginx Proxy Manager, Traefik, or Caddy) or wrap each service in a minimal add-on that just proxies to your LAN host. That way you can still benefit from ingress while keeping the system’s boundaries intact.