Every role, channel, permission and emoji you'd otherwise rebuild by hand — saved, previewable and ready to restore.
A full structural snapshot
Name, icon, banner, description, verification, notification defaults, explicit content filter, AFK channel and timeout, system channel and its flags, safety alerts channel, locale, boost progress bar, vanity URL, and widget settings. Roles keep color, permissions, hoist, mentionable, exact position order, unicode emoji, and icon. Channels keep type — text, voice, forum, announcement, stage — plus topic, NSFW, slowmode, bitrate, user limit, video quality, archive duration, forum tags and layout, and parent category.
Overwrites for every role
Each category and channel stores allow and deny bits per role, and they are remapped to the new role ids on a cross-server restore. The preview shows them as a Discord-style inspector and as a roles-by-channels matrix, so a hidden staff channel does not surprise you after a restore.
Emoji, stickers, soundboard — real assets
Emoji, stickers, and soundboard sounds are stored as the actual image and audio bytes, so they re-upload even if the source server is gone. Member permission overwrites restore on same-server restores.
Server features, not just structure
Auto-moderation rules, scheduled events, onboarding prompts, the welcome screen, webhooks, and the ban list can all be captured and recreated. Pinned and recent messages are reposted through a temporary webhook so author names survive; messages are Premium.
Member roles come back too
Optionally capture which roles each member held. On a same-server restore GuildVault re-assigns them — the raid-recovery case. Cross-server restores skip this since the members are different people.
Diff, then restore
Compare a backup with the live server or with another snapshot. Added, removed, and changed rows are color-coded. The restore stepper asks for a target, what to include, and whether extras on the target should be deleted.
Limits that the bot shares
Free, Basic, and Premium are defined once. The dashboard, the API, and slash commands call the same helper. Hitting a cap returns an upgrade reason, not a silent failure.
Real work, real progress
BullMQ runs when Redis is set; without Redis the app runs the same collector and applier in-process. Every restored item lands in the job report as a success or a named failure — a restore never claims it finished what Discord rejected.