Get 20% off your first order using the coupon code
Built for plugin stacks rather than vanilla defaults. BepInEx loads on startup, every plugin config opens in the browser, and you decide when the game build moves forward.
from $5.00/mo · unlimited slots
Enterprise hardware and every feature you need, at a fraction of the price. Not feeling it? We offer a no-questions-asked 7-day refund window.
Need more than 50 GB of NVMe? Just ask.
Keep up to ten backups at once.
Split your server into more than one.
Switch to any supported game, any time.
Modpacks, worlds, mods and plugins.
Every version, mod, and modpack.
We'll tell you when and why it crashed.
No AI or bots here. Only humans.
6 GB at $15.00 suits roughly ten modded vampires, 8 GB at $20.00 is the popular pick for public plugin servers, and 16 GB at $40.00 carries a full 40-player world.
Every plan: Unlimited Slots · Unmetered Allocations/Ports · Unmetered Databases · Enterprise Hardware · Unmetered NVMe Storage
Need help choosing? Talk to a human or check the docs.
Castle simulation and plugin hooks push single-thread CPU while clan growth drives memory use, which is why FSH pairs Ryzen 9 chips with DDR5 ECC memory and 5 cores from 12 GB up.
The loader is in place from the first boot, so your opening job is uploading plugins rather than wiring up a doorstop.
Instant setup · Loader preinstalled · Mod from day one
Each plugin writes its own .cfg file on first launch, and the panel opens all of them for editing without an SFTP client.
Browser editing · Config folder · Restart on save
Territory simulation, servant missions, and scripted plugin events run on Ryzen 9 hardware with DDR5 ECC memory.
Up to 5 cores · DDR5 ECC · NVMe SSD
Player slots are unlimited on our side, so your connected-user limit is purely a line in your own settings file.
Unlimited slots · Admin tools · Clan settings
DDoS filtering is standard on every server, and the published SLA sets a 99.9% monthly uptime target.
DDoS included · 99.9% target · 24/7 support
Nine game-server regions across North America and Europe, including Ashburn, Toronto, Brussels, and Frankfurt.
9 regions · EU and NA · Pick at checkout
A modded V Rising server is two layers: the BepInEx loader that hooks the game process, and the plugin DLLs it reads from the plugins directory. Upload your DLLs through the panel file manager or over SFTP, drop dependencies such as VampireCommandFramework or Bloodstone in beside them, and restart. The live console prints each plugin as it loads, which is the quickest way to spot a missing dependency before your clan does.
Some plugins are server authoritative and your players never notice them at all. Anything that changes the interface, adds commands with visual feedback, or alters models generally needs the same version on every client, and a mismatch surfaces as a rejected connection or quiet desync. Keep a pinned version list beside your plugins, and use the one-click version changer to hold the game build steady while an author catches up.
Beyond plugins, V Rising exposes its own settings files for the things clans argue about: castle heart limits, blood essence drain while offline, decay timers, clan size, and whether the world runs open PvP or duels only. Edit them in the file manager, restart from the console, and let the task scheduler handle recurring restarts. Ten rolling backups cover you when a settings change turns out badly.
Compare all 9 game server locations for node hardware and the regions each one covers.
Common questions about running a V Rising BepInEx server with us.
Plugins add overhead to a game that already likes memory. Six gigabytes at $15.00 handles a small clan comfortably, 8 GB at $20.00 is the tier most modded servers settle on, and 16 GB at $40.00 with 5 cores suits a busy public world running a long plugin list alongside several large castles.
It depends on the plugin. Server-authoritative mods that adjust drop rates, decay, or admin commands run entirely on our side, and clients connect normally. Anything drawing interface elements, adding map markers, or replacing models needs the matching version locally. Publish your plugin list with version numbers, and rejected connections stop being a mystery.
Take a manual backup, then use the one-click version changer to hold the server on the build your plugins support while authors update. A rollback leaves the save itself untouched, and automatic daily backups keep ten rolling copies regardless. Once the plugin set catches up, switch forward and watch the console for load errors on that first start.
FSH does not meter slots, so the number comes from the connected-user limit in your own settings file. Most operators run somewhere between ten and forty depending on map pressure and how much castle space is left. Plugins that add territory management or extra hearts affect how many people the world realistically supports more than the raw cap does.
Yes. Stop the server, upload your save directory through the file manager or SFTP, and copy your settings files alongside it so the world loads with identical rules. Put your plugins and their config files in place before the first start so nothing regenerates defaults over your tuning, then check the console once and the clan logs into the same castles.
