Find what Rust updates break
Every forced update, WipePilot cross-checks your plugins against uMod, Codefling and Lone.Design, then sends the verdict to Discord within minutes.
The first Thursday of every month, the forced update breaks plugins. The question is not whether it will, but which ones.
A radar keeps watch over your stack
The moment a forced update is detected, WipePilot cross-checks every plugin you run against uMod, Codefling and Lone.Design. Confirmed compatibilities, published patches or open threads: everything reaches you already sorted.
Built to stay outside your server
The forced update breaks things inside your server, sometimes the very plugins meant to automate the wipe. WipePilot never lives there: it runs on its own and keeps watching from the outside, so the update that takes down your stack cannot take down the tool that reports on it. One view, across every server and every host.
The verdict lands on Discord,
not in your tickets
The report fits in one line: 42 OK, 3 patched, 2 broken, with links to the patches and the issue threads. The manual check that used to take one to three hours is down to a few minutes.
What to know before signing up
What will it cost?
Public pricing will be announced at launch. Signing up for early access commits you to nothing: it's one email, not a subscription.
What do the first 50 admins get?
First access to WipePilot, a permanent founder badge, and a real say on the roadmap. Early access is limited to 50 admins so that every founder gets real attention.
What happens after I sign up?
Nothing, by design: you'll receive a single email at launch, with your access.
The next first Thursday is coming
Early access is limited to the first 50 admins.