Private Rust Server Hosting: A Friends-Only Setup Guide

Before your friends build a base, try joining their Rust server with an account that should be refused. A private-server label or a small slot limit will not keep strangers out.

For Rust PC, Facepunch documents a whitelist plugin, or a zero-player limit combined with the built-in skip-queue list. Choose an admission rule and test it, then agree on the map, wipes and co-op settings. Facepunch’s access-control guide

Choose and test who can join

For a whitelist plugin, check support for your installed Oxide or Carbon version. Follow the plugin’s Steam-ID permission instructions and confirm it loads without errors.

The built-in alternative sets server.maxplayers to 0 and grants chosen accounts skip-queue access. Admins can also join, so review the admin and skip-queue lists together. Follow Facepunch’s procedure; a small positive player limit does not perform the same access check.

Use an allowed account and a separate unlisted account to test both outcomes. Repeat after framework or admission-plugin updates. Keep configuration and permission data in a recoverable backup, and restrict access if the rule fails or the plugin stops loading.

Browser visibility and admission are separate

Facepunch’s hidden-server procedure restricts query traffic and assumes administrator/root access. The address can still become public. Check your hosting model’s controls before changing rules, and retain the admission check even if the listing disappears.

For an unintended disappearance, use the Rust server-list diagnosis.

Our VYKIX managed Rust plan provides game-file access, console control and Oxide/Carbon workflows in VXPanel. You still configure permissions and test admission after installing the framework.

Choose a wipe schedule the group understands

Facepunch’s published 2026 PC cadence puts the monthly update on the first Thursday. Plan for required map resets, then choose any extra wipes with your group. Read the release announcement before deleting data. Facepunch’s 2026 schedule

Set map and blueprint policies apart. You can retain blueprints when a release allows it, but Facepunch has required resets too. Its November 2025 announcement did not commit to a permanent monthly blueprint-wipe policy. Leave room for later requirements when promising the group what will survive. Blueprint-wipe announcement

VXPanel supports scheduled force wipes, map wipes, restarts and maintenance. Check the actions, backup and framework compatibility before relying on a job. Use the Rust wipe guide for 2026 planning dates and verification.

Pick the map before building on it

A smaller server.worldsize can shorten travel, but ask whether the group wants compact monument routes or space to explore and build apart.

Generate and inspect the proposed map. Check required monuments, spawn access and routes before committing to the seed. To change the size of an occupied world, preserve its save and plan a new map; editing generation settings does not shrink the existing world.

Adjust rates and co-op rules deliberately

If gathering takes more of the session than the group wants, compare a modest multiplier with current play. Treat 2x or 3x as experiments. Reducing decay changes upkeep and how many structures remain, so include those effects in the decision.

Rust has native PvE behavior through server.pve. TruePVE applies its own configurable damage rules and requires that native setting to be false. Use the PvE setup guide to choose and test the rules with non-admin accounts.

Optional addition	What to verify
Whitelist plugin	Framework support, Steam-ID permissions and rejection of an unlisted account
TruePVE	Damage rules and exceptions for the entities your group uses
Raidable Bases	CopyPaste, prepared base files and the chosen edition’s features
Inventory, kits or teleport plugins	Author instructions, permissions and whether they fit the group’s rules

Check TruePVE’s author documentation and Raidable Bases’ requirements. Add one plugin at a time, test it and back up its configuration and data. Check each extension’s framework support rather than assuming it matches the plugin.

Compare hosting by the work you want to own

A spare PC can serve the group if it meets the workload and networking requirements. Someone must keep it available at play time, update it and recover the files. Your ISP determines public reachability and upstream protection; expose only the needed services.

With managed hosting, we take on host-OS maintenance and protection rules. You still own admission, mods and the group’s reset policy.

The listed VYKIX managed Rust PC plan names the VX-BM-I9-14900K-OC build, player slots, DDR5 memory and NVMe storage under fair-use terms, plus a 10G network port. It includes VxShield, file access, Oxide/Carbon support and three same-server backup slots. Keep an external copy as well. Check the paid configuration and order total, including applicable taxes and fees.

Compare billing periods and extras in the Rust hosting cost calculator. For an existing server, confirm migration scope and eligibility with us first. Assistance is complimentary and best effort; a seven-day switching bonus depends on the qualifying conditions.

Use the trial for a defined group test

The free Rust PC trial runs for 48 hours. A valid card is required for fraud verification, with no trial charge or automatic paid conversion. Service is suspended at 48 hours and active data is deleted seven calendar days after suspension. Export needed files before expiry. Continuing needs a separate paid order, and trial hardware can differ from the paid configuration. Trial and migration terms

🎮 A useful group test covers both admission outcomes, the chosen map, required plugins and a normal session together. Keep those results beside what remains untested: several wipes and performance on a different paid machine.

Compare the Rust plan and start the 48-hour trial.