I run my automations as C# apps in NetDaemon, in "source-deploy" mode - it compiles the .cs files at startup instead of loading a pre-built DLL. The downside of that mode is that a single typo stops the whole process from compiling, so every app is down until it's fixed.
I built a small custom integration to make that less annoying: a sidebar panel in Home Assistant where I can edit the .cs files directly, trigger a reload, and see whether NetDaemon is actually running and whether the last edit compiled - all from the HA frontend, so it also works from outside via Nabu Casa without needing a custom VPN.
It grew a bit from there. There's a button to regenerate the typed Home Assistant entities (what nd-codegen normally does from the command line), an optional log view for when something doesn't compile and I want to see why, and an optional relay that turns an incoming webhook into a Home Assistant event a NetDaemon app can subscribe to.
One thing I paid attention to: none of this needs access to the Docker socket or API. Regenerating entities runs as a plain subprocess inside NetDaemon itself, and the log view reads one specific, read-only bind-mounted log file - giving Home Assistant broader access to the host felt disproportionate for what those two features actually need to do.
It's on GitHub, installable via HACS as a custom repository:
README/architecture docs are in the repo; I also wrote it up in German on my blog if that's useful to anyone: NetDaemon Toolkit: NetDaemon-Apps direkt aus Home Assistant heraus verwalten - Markus und Felix Stephany | Blog
This only makes sense if you're already running NetDaemon in source-deploy mode, so it's a pretty narrow audience - but if that's you, curious whether it's useful, and happy to hear about bugs or missing bits.