Skip to content
+1 (813) 212-3723 [email protected]
Game servers

Root access, included mitigation, no tick-rate surprises.

Run Minecraft, Valheim, and other game servers on isolated KVM vCPU with always-on DDoS mitigation from Tampa.

Compare plans Test latency
Why this platform

Tick-rate workloads need a real VPS, not a game panel SKU.

You get root, public ports, and mitigation that is already on. Mods, custom JARs, and backup scripts are ordinary SSH work, not a support ticket.

DDoS at the edge

L3/L4 mitigation is on for every IP. There is no extra product to enable the night a server goes public.

L3/L4Every IP

Vanilla to modded

gc.micro fits small vanilla worlds and friend servers. gc.medium is the usual step up for heavier mods and more players.

MinecraftValheimMods

Full root

Install the jar, the mods, and the watchdog you want. Custom startup scripts are expected, not a paid add-on.

SSHCustom JARs

Tampa routes

Southeast US, Caribbean, and Latin American paths from the live Tampa region. Test from the looking glass before you buy.

Looking glassMulti-homed BGP
How it works

A server you can actually operate.

Order the size the world needs, open the ports, and copy the world off the box before you install a pack that might not boot.

1

Pick RAM first

Vanilla friend servers often start on gc.micro. Modded packs and bigger player counts usually want gc.medium.

2

Install the stack

Java, SteamCMD, or a dedicated binary. You have root, so the upstream docs apply as written.

3

Open the game ports

Firewall the host yourself. Public UDP and TCP are allowed; mitigation sits in front of the IP.

4

Copy the world off first

Take a snapshot or copy world files off the server before a pack update. Keep a copy off-box anyway.

Step 3 on the host: open only the game ports

sudo ufw allow 22/tcp       # keep SSH open before you enable the firewall
sudo ufw allow 25565/tcp    # Minecraft: Java Edition
sudo ufw allow 19132/udp    # Minecraft: Bedrock Edition
sudo ufw enable
sudo ufw status verbose

Open only the edition you run. If the server's inbound policy is Deny on its Firewall tab, add the same ports there too. Help center: Cloud firewall and DDoS mitigation.

Plan fit

RAM and player count decide the tier.

Start on the size that boots the pack cleanly. Upgrade when the tick rate actually needs it.

gc.micro

Vanilla and friend servers

Small worlds, light mods, and a handful of players.

  • 1 vCPU
  • 2 GB RAM
  • 40 GB SAS SSD
gc.medium

Modded and busier servers

Heavier packs, more players, and worlds that need headroom.

  • 4 vCPU
  • 8 GB RAM
  • 160 GB SAS SSD
gc.xlarge

Large communities

Busy networks, proxies, and worlds that should not share a gc.medium box.

  • 8 vCPU
  • 32 GB RAM
  • 500 GB SAS SSD
Sized example: gc.medium

A modded Minecraft server for a community

Modded packs hold far more in the Java heap than a vanilla world. 8 GB leaves room for a large heap beside the operating system, and 160 GB holds the world, the mods, and a copy taken before each pack update. A vanilla world for a few friends starts on gc.micro.

Deploy gc.medium
  • 4 vCPU
  • 8 GB RAM
  • 160 GB SAS SSD
  • $15.00/mo ($0.0205/hr)

Need exact specs and order links?

Compare game server plans
FAQ

Frequently asked questions

Straight answers on billing, the platform, and what is included on every plan.

Full FAQ

Which plan fits a Minecraft server?

Small vanilla servers often start on gc.micro. Modded or larger player counts usually need gc.medium or higher.

Is DDoS protection included?

Yes. L3/L4 DDoS mitigation is always on for every VPS at no extra cost.

Can I upload custom server files?

Yes. Full root access lets you install mods, plugins, and custom startup scripts.

Ready to deploy a VPS?

Tampa is live. Pick a plan, pick an OS, and the server is online in under a minute.

View pricing Talk to us