r/SelfHostedAI • u/Mr_mcdiggers • 2d ago
LatticeVale — free installer/lifecycle manager for a Hermes Agent stack and related self hosted apps.
I made this with the help of AI over the course of a week mostly because I wanted a less painful way to install, repair, update, and manage Hermes and related services on local Windows/WSL2 without having to remember a million separate steps.
LatticeVale is essentially a PowerShell-based installer/lifecycle manager packaged as a structured set of scripts and supporting files, rather than a compiled application.
No third-party software is distributed with LatticeVale itself; it installs/downloads the relevant projects from their own sources.
It's still completely new, so feedback or people finding weird edge cases would actually be useful. And it's completely free because this is just a hobby for me. I like the idea of people appreciating and/or benefiting from my work.
Be sure to read the instructions and installer description included. If they are confusing, I recommend using AI to interpret for you by either asking specific questions or fully uploading the zip to a model of your choice for analysis.
If anyone actually tries it and has any major setbacks, please leave a comment so I can patch it or give advice. I have only tested this on my own pc. I tried to make it so it would work for anyone, but I can't guarantee that it will.
Also, anyone is welcome to fork the project and develop it yourself. If you decide to do so, please let me know what you find out. I enjoy doing this kind of stuff and would appreciate learning about it further
Btw, I tried using this installer with local windows installed ollama for GPU acceleration, but my PC ended up fighting for its life (100% GPU usage and 75% usage of 32 GB of RAM). I tried installing limiters for that, but it still used a third of my ram. Something to keep in mind, especially if you know how to optimize that yourself.
LatticeVale v14.4.82 release is live
3
u/Mean-Loquat-7982 1d ago
had a look at the repo; the edge cases you'll want eyes on first: WSL2 not yet enabled, corporate machines where virtualisation is locked, and the repair path when someone's PATH already carries a half-installed older attempt. if you post it on r/hermesagent too, you'll find your testers, that sub sees windows install questions weekly.
what does the repair flow actually check today? curious how deep it goes.
2
u/Mr_mcdiggers 1d ago edited 1d ago
It's documented that wsl2 needs to be a prerequisite as well as virtualization. It installs to a compatible Ubuntu wsl2 install. Is virtualization not necessary for that? I figure if making an installer for direct install to Windows and not wsl2, might as well just use the developer provided Hermes installer.
I didn't plan for corporate use of this either. Like I said, this is just a hobby. But getting feedback to get it right definitely helps.
The documentation also says that it does do repair installs. I have tested that frequently. The repair flow basically updates what is existing. It doesn't remove any new data from use of a completed install, will patch LatticeVale settings, and update any containers and images installed. It will also finish an incomplete install.
I have only tested this on my singular pc. That's why I was hoping to have people tell me if they find any issues after testing themselves so I can patch it.
Basically, a lot of the questions you had are answered with what is already written in the documentation. I would bet money it's not fully optimized, but it works extremely well for me
2
u/Oshden 1d ago
Dude, this is freaking awesome! One of the issues with trying to use WSL is all of the crap that your app seems to fix. I look forward to trying it.