infraweaver/about
About
InfraWeaver started as the answer to wiring the same eight pieces together for the third time, and to the fact that the wiring — not the pieces — is where all the work is.
Everything InfraWeaver installs already existed. Talos, ArgoCD, OpenBao, Traefik, cert-manager, Longhorn, Authentik, Onedev and Kyverno are mature upstream projects with good documentation. What did not exist was the specific arrangement of them where the secrets store is seeded before the operator that reads it, the identity provider is wired into the three services that need it, and the whole thing keeps working after the machine you installed from is switched off.
The design decision underneath all of it: the loop closes inside your cluster. GitHub is a template, read once. After that your git server is the source of truth and ArgoCD reconciles against it. No account, token or third-party service outage is your outage.
It is alpha, honestly labelled, and used daily by the person who wrote it. That is the entire claim.
LICENCE
MIT. Fork it, ship it, change it. The fork path is a documented workflow: your values
live in .env and envs/, upstream ships only placeholders, so
pulling updates into a fork is normally conflict-free.
NOT AFFILIATED
This project is not affiliated with or endorsed by Proxmox Server Solutions GmbH, Sidero Labs, or any other upstream vendor. It installs their open-source software; it does not speak for them.
The one deliberate exception
Everything in InfraWeaver is a variable, filled from your own configuration. Exactly one thing is not, and it is documented rather than hidden.
The console's feedback endpoint is a hardcoded constant with no environment override. Every forked deployment stores user feedback locally for its own admins and forwards a sanitised copy to one canonical endpoint, so maintainers can see what breaks across every fork rather than only in one homelab. A loop-guard header stops the canonical deployment forwarding to itself.
It is stated in the infrastructure README, in this paragraph, and in the code. If that trade is not one you want to make, it is four lines to remove in your fork — which is exactly why it is documented in the open instead of buried.
Start it on a spare box.
A nested Proxmox VM with 32 GB is enough to watch the whole thing come up, and
scripts/redeploy.sh puts you back to zero if it does not.