infraweaver/get started
Get started
Read requirements first if you have not sized the host yet. If you have, the whole install is one command and eight wizard steps.
1. Start the installer
The same URL works everywhere. What it does depends on where you run it.
ON A PROXMOX HOSTRECOMMENDED
The script detects Proxmox and asks whether to create a small dedicated init VM or to run the wizard on the host itself. The VM keeps the hypervisor clean and is thrown away afterwards.
ON LINUX OR MACOS
The wizard starts immediately on port 8080. The machine only needs to reach the Proxmox API on port 8006 — it does not need to be on the cluster network.
FROM A CLONE
If you would rather read the code before running it:
Environment overrides: IW_WORK_DIR, IW_REPO_URL,
IW_REPO_BRANCH, IW_PORT, IW_HOST,
IW_YES=1 to skip prompts.
2. Answer eight questions
The wizard's only output is a .env file. Everything downstream is generated
from it, which is why you can skip the UI entirely and write the file yourself.
| Step | What it asks for |
|---|---|
| 1 Welcome | Prerequisite check against the machine you are running on |
| 2 Domain | Base domain and admin email — every service is served under this domain |
| 3 Proxmox | Host IP and an API token, or root credentials it uses once to mint one |
| 4 Cluster | Node IPs, VMIDs, and per-node CPU, RAM, disk and PVE node assignment |
| 5 Identity | Admin username and SSO settings |
| 6 Credentials | DNS provider token, SMTP, and any optional secrets |
| 7 Features | Optional groups: monitoring, VPN, backups, runtime security |
| 8 Deploy | The button, and the live log |
OR SKIP THE WIZARD
The wizard is a convenience over a text file. If you prefer the text file:
.env.example is the full reference: domain and identity, Proxmox
connection, node IPs and VMIDs, the MetalLB VIP range, DNS provider credentials and
every feature flag.
3. Watch it build
Six stages, roughly ten to fifteen minutes on the default three-node shape. Pick one to see what it runs.
4. The first five minutes after it finishes
-
Open the console at
https://console.<your-domain>Log in with the admin account the wizard created. Everything the platform runs is visible from here. -
Read your credentials out of OpenBao
Nothing was written to disk.
vault kv get -field=bootstrap-password secret/platform/authentik, or use the OpenBao UI on the internal tier. -
Check the internal services resolve
argocd.int,openbao.intandonedev.intunder your domain. If they do not, CoreDNS or your LAN ranges need a look. - Rotate anything you care about Generated credentials are random, but this is alpha software. Treat the first set as a starting point, not a final answer.
- Install one catalog app It is the fastest way to confirm the GitOps loop, the registry, storage and TLS are all doing their jobs at once.
Do this on a spare box first
InfraWeaver is alpha and has had no independent security review. A nested Proxmox VM with 32 GB is enough to watch the whole thing come up, and nothing you care about is at risk while you decide whether you trust it. Read security before pointing a real domain at it.