Melissa: agents handle your homelab services A developer released the first public demo of Melissa, a utility that manages a homelab machine and launches subagents to set up services such as Nextcloud and Minecraft, including handling issues like occupied ports. The developer disclosed that Melissa was built with AI, that little thought went into security, that no update strategy exists beyond pulling and rebuilding, and that it should not be exposed to the open web or relied on yet because many features are missing. Stated future goals include multi-machine Melissa instances communicating over a Tailscale network and dividing services among themselves, plus agent-isolated Nix and microVM services. Last Wednesday i started developing this utility that helps someone set up services using AI. Today I’m releasing the first public demo. Melissa manages your homelab box and launches subagents that handle services you want. Nextcloud, Minecraft, Even some random stuff i found. It’s able to deal with various issues that can result from occupied ports. Screenshot: AI disclosure: yes this was developed with AI. Security disclosure: i started developing this last Wednesday, there wasn’t that much thought put into security, mostly getting a demo out to users. Please don’t expose this to the open web. No update strategy besides pulling and rebuilding is developed either. Reliability disclosure: I can’t stop you, but you really shouldn’t rely on it yet , a lot of features are missing. I generally want to imagine that this utility will be useful for people who are able to get devices similar to the DGX spark. I can’t get one of these myself. In the future however they will have to eventually get cheap enough that any household is able to grab one of these. Futures Goals: Eventually i want to have a piece of software so simple where a person can just get a box with it, plug it in a wall and in 5 minutes have his agents running around setting up his minecraft servers and nextcloud and whatnot. I want to have different computers running melissa communicate via a tailscale network probably tailscale and divide services among themselves. For example one melissa can decide to handle nextcloud because it has storage, another one can decide to handle backups, a third one might decide to run a minecraft server. Theoretically you should also be able to have one running in a remote service running as an exit node for the entire melissa network. I also want to see if it’s possible to have agent isolated nix services and microvm services.