Rust recruitment happens in bursts. The week before a wipe you get fifty applicants, and the week after you get none — and every one of those fifty needs to be assessed on hours, timezone coverage and whether they will still be online on day four.
No card required · Free plan available · Set up in an afternoon
Rust
Survival & Sandbox
Also searched as
Rust clan · Rust server · Rust RP · wipe day · Rust team
Fifty applications the night before wipe, all in one Discord channel
No way to verify hours or check someone actually owns the game
Officers duplicating work because nobody knows who reviewed what
Guildbase gives Rust clans and servers a real application system: Steam verified applicants, questions that actually predict retention, a shared review queue your officers can work through together, and Discord roles applied the moment someone is accepted.
Every one of these is its own template with its own questions, requirements, reviewers and workflow. Build the ones you need and ignore the rest.
Your core intake: hours, timezone, roles they play, and whether they can commit to grind schedules and raid times.
For RP and low-pop servers that gate access, with rule comprehension and a short screening on playstyle.
Recruit server admins with questions on handling cheat reports, abuse of powers and dealing with raid disputes.
Run the end of a trial period as its own tracked application so the decision to keep someone is recorded, not vibes-based.
Let other clans formally request an alliance with a roster and terms, rather than a DM to your leader.
Handle appeals through the ticket system with a clear record of the original ban and the appeal outcome.
The features that matter when you are running intake for Rust, not a generic form builder.
Require a linked Steam account before an application can be submitted, so you know who you are actually talking to.
Filter, search and assign the flood of pre-wipe applications across your officer team, with clear reviewer assignment so nobody duplicates work.
Clan and trial roles applied automatically, applicant role removed, nickname set to your tag format — all as one workflow action.
Model trial periods as workflow stages so a member moves from trial to full only when an officer moves them, with a recorded decision.
Stop denied applicants reapplying the following wipe with a cooldown, and gate reapplications on previous outcomes.
See where your applicants come from and how many convert, so you know whether your recruitment posts are actually working.
See the full platform feature list, or compare what is included on each plan on the feature comparison page.
Sign up with Discord, Google or email, create your community and connect your Discord server.
Drag your questions into place, or start from a community template someone has already built for Rust.
Decide who can apply, add review, interview and exam stages, and choose which Discord roles get applied at each one.
Post your public page in Discord and your server listing. Applications land in a queue your whole staff team shares.
Browse community templates to start from a form someone else has already built and tested.
Steal these. They are the questions that separate applicants who will stick around from applicants who wanted to see what was behind the form.
Yes. Steam is one of the supported login connections, and you can make a linked Steam account a requirement before an application can be submitted, alongside a verified email or a minimum account age.
Every application lands in a single searchable queue that your whole officer team shares. You can filter, assign reviewers, leave internal notes and process the burst as a team rather than everyone reading the same Discord channel.
Yes. Model the trial as a workflow stage. Accepted applicants get the trial role automatically, and moving them to the full member stage swaps the roles over and records who made the call.
Yes. Servers use it for whitelist applications, admin and moderator recruitment, and ban appeals through the ticket system, all under the same branded portal.
That is up to you. Application cooldowns let you set the waiting period after a denial, and requirements based on previous outcomes let you block or allow reapplications explicitly.
Yes. The free plan covers one clan or server with two application templates, which is enough for a recruitment form and an admin form. Larger communities upgrade for unlimited templates and staff.
Still stuck? The help centre covers setup step by step, or ask in our Discord.
Whitelist, group and staff applications for DayZ roleplay and hardcore survival servers.
Tribe recruitment, cluster whitelist and admin applications for ARK servers and competitive tribes.
Whitelist applications for SMPs, staff and builder recruitment, and event signups for Minecraft servers of any size.
Free to start, no card required. Bring your Discord server and your first form can be live today.