infraweaver/comparison
Comparison
InfraWeaver is not the right answer for everyone. Here is what it is genuinely better at, what it is worse at, and when you should pick something else.
Against wiring the same stack yourself
The closest comparison, because it is the same components. The difference is who does the integration and who maintains it.
| By hand | InfraWeaver | |
|---|---|---|
| Time to a working cluster | A weekend if you have done it before, a month if not | Ten to fifteen minutes after the wizard |
| Component choice | Entirely yours | Opinionated. Swapping Traefik or Longhorn means editing the platform, not a config flag. |
| Secrets | Whatever you set up, which is often nothing | OpenBao plus External Secrets, wired on the first boot |
| SSO across services | The job everyone postpones | Authentik, wired into ArgoCD, Grafana and Onedev by the installer |
| Rebuilding after a mistake | Depends how good your notes were | One documented script, from the same .env |
| Understanding what you run | Total — you built it | Requires reading. The manifests are all there, but you did not write them. |
Against a managed Kubernetes service
WHERE INFRAWEAVER WINSFOR THIS
- Hardware you already ownNo per-node fee, no egress bill, no capacity you rent twice.
- Data stays on your premisesIncluding the git server, the CI runner and the secret store.
- Nothing to depend onAfter install there is no upstream account, token or service whose outage is your outage.
- The whole platform, not just the control planeIngress, TLS, storage, identity and CI are installed and wired, not left as an exercise.
WHERE IT LOSESBE HONEST
- You are the on-callNo provider is watching your etcd at 3am. That is the deal.
- No SLA, no support contractAlpha software maintained in spare time. There is no number to call.
- Control-plane upgrades are yoursTalos makes this far less painful than it used to be, but it is still a task on your calendar.
- Physical failure is physicalA dead disk is a trip to the cupboard, not a support ticket.
Against a single-box NAS or app-server OS
Systems in this shape run applications on one machine with a good UI. That is a genuinely better fit for a lot of homelabs, and pretending otherwise would be dishonest.
| If you want… | Pick |
|---|---|
| Storage first, with apps as a bonus, on one box | A NAS operating system. Filesystem features and disk management are its whole purpose; they are not InfraWeaver's. |
| A friendly app store on one machine, no clustering | A single-box app platform. Far less to understand, far less to go wrong. |
| To manage containers you already run | A container management UI. It sits on top of what you have instead of replacing it. |
| An app to survive a node dying | InfraWeaver. Three nodes, replicated storage, and a scheduler that reschedules. |
| Every service behind one login | InfraWeaver. SSO across the whole platform is installed, not assembled. |
| Your infrastructure described in git, reconciled continuously | InfraWeaver. This is the part the others do not do at all. |
If your homelab is one machine and you want it to stay one machine, InfraWeaver is overhead you will feel every day. If you have three machines' worth of hardware, want things to survive one of them failing, and would like the whole arrangement described in git instead of in your head — this is what it is for.