Is WolfStack Right For You?
WolfStack is a single-binary management plane for clusters of Linux servers — Proxmox, plain Ubuntu/Debian, Arch, Rocky — with built-in container, VM, networking, storage, backup, monitoring, status-page, and overlay-network features. The honest answer to “should I run this?” depends entirely on what you already have. This page is the briefing we wish every new user got before they ran the installer.
Bottom line up front: WolfStack is at its best on bare metal or mixed clusters where one team wants a single pane of glass for everything — VMs, containers, networking, backups, alerting, status pages. If you already operate dedicated tools for each of those layers, you will turn most of WolfStack off. That is fine. Some pieces (WolfRouter, WolfNet, status pages, threat intel) are still worth running standalone.
Where WolfStack shines
- Greenfield homelab or small-business cluster — you have hardware, you don’t want to glue eight tools together, you want one binary that boots and works.
- Proxmox shops that want a friendlier multi-cluster view — WolfStack discovers PVE certs, talks to PVE’s API, and gives you a single UI across multiple PVE clusters plus non-PVE nodes.
- Mixed VM + LXC + Docker fleets — WolfStack treats Docker, LXC, and KVM as first-class and shows them on one page with one orchestration story (WolfRun).
- Teams that want zero-config clustering — nodes find each other, share state, and a built-in WireGuard-based overlay (WolfNet) wires them together without a separate VPN to operate.
- Edge / hosting / MSP scenarios — status pages, alerting, AI assistant, threat intel, and per-cluster isolation are baked in rather than bolted on.
Where WolfStack will overlap with what you already run
If you read the list below and recognise yourself, that does not mean WolfStack is wrong for you — it means you should plan to run it in a reduced-footprint mode and turn off the features you already have covered. We recommend the agent-only install and disabling individual subsystems on each node.
| Already running | WolfStack overlap | Recommended posture |
|---|---|---|
| Proxmox VE | VM/LXC management, clustering, backup scheduling | Run WolfStack as a complementary management plane — it talks to PVE’s API and discovers existing certs. Keep PVE’s own scheduling for VMs. |
| Komodo / Portainer | Container orchestration, compose UI | Pick one. Running WolfRun and Komodo against the same Docker socket leads to surprise restarts. If you have a working Komodo, keep it — use WolfStack for the layers Komodo doesn’t touch (networking, backups, status pages). |
| Grafana + Prometheus + Loki | Built-in monitoring, alerting, log viewer | Disable WolfStack alerting and use Grafana-side alerting. WolfStack’s status pages and AI summaries still add value on top of your existing stack. |
| Unraid | Storage, share management, Docker, VMs, app store | WolfStack and Unraid both want to own the box. We don’t recommend installing WolfStack on an Unraid host directly. Run it on a separate node alongside Unraid for cluster-wide views and status pages. |
| TrueNAS SCALE | Apps, VMs, storage, sharing | Same as Unraid — don’t install on the TrueNAS host. Mount TrueNAS shares from a WolfStack-managed node and use WolfStack for everything off the appliance. |
| Tailscale / NetBird / ZeroTier | WolfNet overlay | Pick one overlay. Stacking two encrypted overlays on the same NICs causes routing tears. WolfNet is the simplest path if you want it inside WolfStack’s clustering loop. |
| Pi-hole / AdGuard / Technitium | WolfRouter installs dnsmasq on port 53 |
Don’t enable WolfRouter on a host that already binds :53. The installer will warn and offer to skip. Run WolfRouter on a dedicated edge node instead. |
| Nginx Proxy Manager / Caddy / Traefik | WolfProxy reverse proxy | Skip WolfProxy. Keep what you know. |
| UptimeKuma / Statping / Cachet | Status pages | WolfStack’s status pages are cluster-aware and zero-config. We think they’re a fair replacement, but it’s a wash — pick what your team likes. |
What’s worth keeping on, even when most things are off
Even on a heavily-customised stack, these subsystems usually justify keeping WolfStack around because they’re cluster-aware and require almost no configuration:
- Cluster Browser & Cluster status — cross-node inventory and live health, even for nodes you mostly manage elsewhere.
- WolfNet overlay — if you don’t already have a mesh VPN.
- Status pages — public, cluster-scoped, multi-channel notifications.
- Threat Intel + LAN Health — passive scanning and one-click fixes.
- AI assistant — cluster-aware troubleshooting that knows what you have running.
Server install vs agent-only install
WolfStack ships in two installer modes:
- Server install — brings up the management UI on port 8553, the cluster API, and all subsystems. Run this on one node per management domain. This is your “single pane of glass” node.
- Agent install — brings up the cluster API, WolfNet, and the node-side daemons, but does not bind the SPA / management UI. Use this on every other node. They’re fully managed via the server node’s UI through the cluster proxy.
If you have three Proxmox nodes: install the server build on one, agent on the other two. You get one UI and three managed nodes — not three competing UIs.
What we will not pretend to be
- A drop-in replacement for Kubernetes. WolfKube exists for small Kubernetes deployments; if you run multi-tenant production K8s, keep your existing platform.
- An observability stack. Our metrics and logs are good enough to operate WolfStack itself and answer common questions. They are not a substitute for Prometheus/Loki/Tempo at scale.
- An identity provider. Auth is currently against
/etc/shadowwith optional 2FA / passkeys. Enterprise SSO is a separate, paid module. - A NAS appliance. WolfDisk replicates and shares disks across the cluster, but it is not Unraid / TrueNAS, and we do not recommend installing it on top of either.
Pre-install checklist
Before you hit the installer, take 30 seconds to answer these:
- What’s already on port 53, 80, 443, 8553, 51820 on this host?
- Is this host running an opinionated appliance OS (Unraid, TrueNAS, OPNsense)? → install elsewhere.
- Do I want this to be a management node (server install) or a managed node (agent install)?
- Do I already have a working monitoring stack? → plan to disable WolfStack alerting after install.
- Do I already have a working overlay network? → plan to skip WolfNet.
The installer will surface known conflicts (Pi-hole, AdGuard, Technitium, systemd-resolved, bind, existing reverse proxies) before it changes anything. Read the confirmation screen. Don’t auto-yes.
Still not sure?
The honest test: spin up a throwaway VM, run the server installer, click around for an hour. You’ll know within that hour whether WolfStack belongs in your stack. The troubleshooting page covers the most common first-hour gotchas, and the contact page goes straight to us if you want a second opinion before committing real hardware.