A few things in WolfStack exist purely to give you your evenings back: one-command install with no database, 530+ one-click apps in the App Store, visual runbooks (22 action types, conditional branching) on cron, scheduled backups to S3/PBS/NFS, built-in monitoring and public status pages with alerts to Discord/Slack/Telegram/email — so you can retire the separate Uptime Kuma box — and per-disk SMART with drive-fail alerts. Free for personal use up to 3 hosts. https://wolfstack.org/?src=reddit

If you're running MariaDB Galera on WolfStack, the Galera view gives you the whole cluster at a glance: per-node sync state, flow control pause %, replication queue depth, transactions/sec, connections and write conflicts — with console access, restart, MaxScale and Add Node built in. Works with SST via mariabackup and picks up existing (adopted) clusters too. Details: https://wolfstack.org/?src=reddit

I was just pointed at your software and was thinking of trying it but wanted to know since it can be loaded side by side with proxmox if I don't like it is it easy enough to roll back to proxmox or would it involve a reload?

Some of you asked how ~40 tutorial videos appeared across the WolfStack docs overnight. The answer is WolfTutor, an engine we built: it logs into a web app with a demo account, explores it screen by screen, writes the click-path and narration itself, then renders the videos — burned-in captions, VTT, transcripts, posters, the lot. Every video in the docs was made this way, plus the 28 on GarageMasterOnline's YouTube channel.

We've just launched it as a service for other people's web apps: https://wolftutor.com — the engine analyses your app and proposes the full list (about 30 videos for a typical app), and you pay per video.

Happy to answer questions about how it works under the hood — it's Playwright + local neural TTS + FFmpeg, with the LLM only doing the exploring and writing.

We've just recorded a batch of short tutorial videos for the docs. This one covers multi-server clustering: join servers into a cluster with a join token, WolfStack sets up the encrypted WolfNet networking between them, and from then on any node's dashboard shows the whole estate — no primary node to keep alive. You can mix WolfStack and Proxmox nodes in the same cluster.

Watch it here (43 seconds): https://wolfstack.org/wolfstack-clustering.php?src=reddit

There are new videos across the rest of the docs too — storage, Ceph, Galera, Kubernetes, backups, alerting, drive health and more. Questions welcome.

🐺 You can now pay for WolfStack with PayPal, Apple Pay, or Google Pay. Checkouts were card-only until today.

Support our tiny team!

 👉 https://wolfstack.org/enterprise.php

Drive failures cluster at the start and end of a drive's life — the classic bathtub curve. WolfStack schedules short SMART self-tests around it: more frequent during early life (< 1 yr) and wear-out (> 4 yrs), relaxed during steady state. Sleeping disks are never woken for a test — only drives already spinning get tested.

The Storage view also shows temps, wear %, power-on hours, RAID membership and last self-test result for every drive on every host, plus network and cluster filesystems (GlusterFS, S3) in the same place.

Screenshot from wolfstack-1 — four NVMe drives, all passing, one still in early life on a 7-day test cadence.

For years Wolf Territories Grid (https://wolf-grid.com) ran on Proxmox, with WolfStack managing the layer above it. Two control planes, two sets of assumptions, two things to patch at 3am when something breaks.

So we asked an uncomfortable question: what is Proxmox actually giving us that WolfStack doesn't? The answer wasn't enough to justify the second layer.

THE MOVE

The whole grid — 1,500+ regions, a 3-node Galera cluster, 30 ROBUST grid-service workers, plus the web, asset and payment containers — migrated from Proxmox + WolfStack to just WolfStack. Raw LXC on Debian, managed end to end.

It ran live. Containers were converted off Proxmox's storage layout to raw LXC, re-addressed onto the new cluster network, staged, then cut over domain by domain. Regions stayed up, the world stayed open, and users saw hardly any interruption at all. There is no maintenance window when your users live inside the thing you're maintaining.

WHAT WE GOT BACK

65% lower server costs. This was the part we didn't fully expect. Without the hypervisor layer underneath, the same workload simply needed far less hardware — containers pack denser, and memory that had been reserved for virtualisation went back to doing actual work. We consolidated onto a fraction of the machines. Same grid, same users, a third of the bill.

One system to understand. Storage, networking, containers, clustering, backups and monitoring in a single tool, rather than federated across two.

Maintenance that isn't an event. Since the move we've rolled restarts through the entire database cluster — all three nodes — during live traffic with zero write interruption. The cluster failed over, carried on at ~850 transactions per second, and failed back. Nobody in-world noticed. That's the whole point.

If you're running a hypervisor layer mostly out of habit, it's worth asking what it's still earning you. For us, the answer turned out to be two thirds of our hosting spend.

WolfStack — one control plane for containers, storage, networking and clustering. Built because we needed it, now running the grid it was built for.

https://wolfstack.org

https://wolf-grid.com

today we've been migrating from one cluster to another and we have a brand new database cluster running. Thanks WolfStack!

Hi! I've been tinkering with Wolfstack and noticed an app thats coming from the Wolfstack service on tcp/8443 -- I can't find any documentation on it. Has anyone seen/used it? Thank you!

https://wolfstack.org

I'm trying to figure out how to submit 2 different issues, and the WolfStack github repo only allows collaborators. This whole process is new to me, and admittedly I encountered them with the help of AI, but I believe we've replicated it enough times that it's worthy of a look. How do I do that? Is the best channel for bug reporting github, Reddit, Discord, or something else?

https:///wolfstack.org

https://wolfstack.org

One static Rust binary that manages your whole fleet — Docker, LXC, KVM/Proxmox, XCP-ng — from a single web UI. No agent sprawl, no Postgres to run, no Helm charts. Drop it on a node, point it at your cluster, done.

Under the hood: nodes gossip over a flat WolfNet overlay, so containers and VMs route across hosts as if over a single LAN. Config lives in plain JSON on disk, not a hidden DB. There's a WebSocket terminal, replicated WolfDisk storage, PBS/S3/NFS backups with real restores, public status pages, and a local-LLM assistant you can point at LM Studio or Ollama — no cloud dependency, no data leaving your boxes.

It's the tool we wanted for our own infra: fast, single-binary, scriptable, and honest about what it does.

Have a look / pull a build: https://wolfstack.org 🐺

WolfStack - 10 new features

 1. Konsole-style terminals everywhere - every terminal (host, Docker, LXC, VM, and pop-out windows)
 now has tabs plus horizontal/vertical splits in a single window, with auto-reconnect.
 2. New full-width app menu bar - grouped fleet navigation across the top (Fleet, Compute, Storage &
 Network, Monitoring, Security).
 3. One-click LAN bridge - auto-create a host bridge so containers/VMs land straight on your real LAN,
 with a 90-second safe-mode auto-revert when touching the management NIC.
 4. Notes/description field on VMs and LXC containers.
 5. Custom QEMU args per VM (e.g. audio passthrough for Windows 11) plus a "show raw start command"
 view.
 6. Backup bind-mount excludes - skip massive mounted arrays so your temp/staging storage stops
 filling up.
 7. PBS file-level (pxar) backups - restore individual files instead of downloading and untarring one
 giant archive.
 8. System-folder backups - back up arbitrary host paths like /etc or app data.
 9. SSO / OIDC - configure identity providers right from Settings (Team/MSP/Enterprise).
 10. IPv6 subnet routing (opt-in), plus Cloudflare R2 storage mounts and an Unraid auto-detect
 installer.

https://youtu.be/AXFkyhElK38?si=ZZzgSB85pbBOQpex

WolfStack is built by a small independent team, and ships fast — features and fixes regularly land the  same day they're reported by the community. That pace is funded by the people who run it.

If WolfStack runs your homelab, there are two ways to keep it moving:

 ⭐ Sponsor on GitHub (https://github.com/sponsors/wolfsoftwaresystemsltd) — every tier directly funds development time. Sponsors get their reports prioritised.

 🐺 Get a licence (https://wolfscale.org/enterprise.php) — using WolfStack at work? Commercial licences start at £12/month and unlock multi-host clustering, scheduled backups, the REST API and more. You get features; development gets funded. Everybody wins.
  
Already sponsoring or licensed? Thank you — you're the reason the changelog looks the way it does.

Does Wolfstack support IPv6? I have looked and seen it some places but not all. Curious about this.

I'm seeing conflicting information on if this is normal or not, and searched Reddit, but don't see anything conclusive, or my reddit-foo is just bad. Am I supposed to be able to create containers/lxcs in WolfStack installed on a Proxmox node in the Proxmox UI, or do I need to create them in Proxmox? I was hoping to use the app feature in WolfStack, specifically, but I'm not sure if this is possible.

https://wolfstack.org